1 of 18

National Dashboard Service Configuration

Recently Added Properties in ChartApiConfig

Todays Collection

Possible Values: true/false

Supported Chart Types: METRIC

How it Works: This property is added to support the new requirement to show the Date and the last updated time in the Todays Collection Metric Chart

Populating true for isTodaysCollection for any chart config in chartApiConfig.json of type metric chart, MetricChartResponseHandler looks for todaysDate and lastUpdatedTime aggregations with the bucket(s) having epoch in key. These are used as values for todaysDate and lastUpdatedTime respectively and added to plots in the response. The UI framework is used to show the Collection on Date and lastupdate time tooltip.

Sample Response

  "aggregations" : {
    "AGGR" : {
      "meta" : { },
      "doc_count" : 256,
      "todaysDate" : {
        "doc_count_error_upper_bound" : 0,
        "sum_other_doc_count" : 240,
        "buckets" : [
          {
            "key" : 1645747200000,
            "key_as_string" : "25-02-2022 00:00:00",
            "doc_count" : 16,
            "Todays Collection" : {
              "value" : 135.0
            }
          }
        ]
      },
      "lastUpdatedTime" : {
        "doc_count_error_upper_bound" : 0,
        "sum_other_doc_count" : 16,
        "buckets" : [
          {
            "key" : 1646316682170,
            "doc_count" : 16
          }
        ]
      }
    }
  }

Sample Query

{
  "aggs": {
    "AGGR": {
      "filter": {
        "bool": {}
      },
      "aggs": {
        "todaysDate": {
          "terms": {
            "field": "date",
            "order": {
              "_term": "desc"
            },
            "size": 1
          },
          "aggs": {
            "Todays Collection": {
              "sum": {
                "field": "todaysCollectionForPaymentMode"
              }
            }
          }
        },
        "lastUpdatedTime": {
          "terms": {
            "field": "lastModifiedTime",
            "order": {
              "_term": "desc"
            },
            "size": 1
          }
        }
      }
    }
  }
}

preActionTheory

Possible Values: Map the key as one of the aggregationPaths and value as compute Helper

For instance -

"preActionTheory":{
      "Actual collection":"repsonseToDifferenceOfDates"
    }

Supported Chart Types: METRIC

How it Works: Metric Chart Type has the action property. Possible values include percentage or undefined. On Collecting the aggregationPath values -

the percentage is calculated if the action is a percentage
all aggregation values are summed up if the action is undefined

For TargetAchievement there is a requirement to apply repsonseToDifferenceOfDates compute helper on one of the aggregation path values before applying action.

The preaction theory helps to apply to compute helper before actually applying the action.

According to the above example, responseToDifferenceOfDate Compute helper is applied to the value of the Actual Collection aggregation before applying percentage calculation on all aggregation values. National Dashboard UI Tech Documentation:

National Dashboard - UI Technical Documentation

National Dashboard - UI Technical Doc

Overview

A decision support system (DSS) is a composite tool that collects, organizes and analyzes business data to facilitate quality decision-making for management, operations and planning. A well-designed DSS aids decision-makers in compiling a variety of data from many sources: raw data, documents, and personal knowledge from employees, management, executives and business models. DSS analysis helps organizations identify and solve problems, and make decisions.

Key Concepts

Type Of Users

National Level Admin (NATADMIN)
State Level Admin (STADMIN)

Dashboard List

There are three types of dashboards -

Home page (refer to figure 1).
Overview page (refer to figure 2).
Module-level dashboard (refer to figure 3).

The home page contains multiple cards - each card is clickable.

There are two types of cards, i.e, Overview cards and module-level cards.

Overview and Module level card is differentiated by vizType,

Overview card: Clicking on the Overview card, redirects users to the overview page. vizType for Overview is a collection.
Module Level card: Clicking on the Module level card, redirects users to the Module level dashboards. vizType is module (i.e Property Tax, Trade License etc).
Map chart: This entity displays the total, active ULBs within states where DIGIT is live.

Configuration Details

Enable national dashboard: MDMS details

Enable the NDSS in the city module.

Request Payload For Dashboard Config

https://qa.digit.org/dashboard-analytics/dashboard/getDashboardConfig/NURT_DASHBOARD

auth-token: authenticates the request and fetches from the local storage key called Employee.token

DashboardConfig API Response

National DSS Chart Details

Visualizations: The key contains all configurations for displaying the visualization like rows with charts etc. - refer to figure 1.3. In Figure 1.3, the vizType key defines the module UI.

For Collection Chart & Module Chart refer figure 1

Visualizations List

In the dashboardConfig response visualizations key contains all rows & charts details (refer to figure 1.3).

Each row contains visual details like name, vizType, noUnit, charts etc.(refer to figure 1.3).

name - the name of visualization

vizType - the type of visualization like COLLECTION, MODULE, METRIC-COLLECTION, PERFORMING-METRIC, CHART

COLLECTION - contains collection data and is displayed on the home page (refer to figure 1)
MODULE - contains module-level data and is displayed on the home page (refer to figure 1)
METRIC-COLLECTION - contains collection data and is displayed on Overview/Module level page (refer to figure 2.1)
PERFORMING-METRIC - contains top/bottom performing data displayed on Overview/Module level page (refer to figure 2.2).
CHART - contains the below visualizations displayed on Overview/Module level page (refer to figure 2.3 to figure 2.7).
1. PIE CHART (refer to figure 2.3)
2. LINE CHART (refer to figure 2.4)
3. BAR CHART (refer to figure 2.5)
4. HORIZONTAL BAR CHART (refer to figure 2.6)
5. TABLE CHART (refer to figure 2.7)

List of visualizations

Figure: 2.1 Collection Metric

Figure: 2.2 Performance Metric

Figure: 2.3 Pie Chart

Figure: 2.4 Line Chart

Figure: 2.5 Bar Chart

Figure: 2.6 Horizontal Bar Chart

Figure: 2.7 Table Chart

Figure: 2.8 Global Filters

Figure: 2.9 Download & Share Button

Global Filters (figure 2.8)

State is fetched from stateCode ULB from code

Denomination filter: Denomination filter offers three options to display the amount and number in a particular format.

Crore
Lakh
Unit

Denomination filter is not applied on the percentage and text (figure 2.10). Type of data is identified by symbol in plots of charts API.

Figure 2.10

Custom Date Filter

If the duration is < 15 days, data is displayed days-wise.

If duration <= 30 days, data is displayed week-wise.

If duration >30, data is displayed monthly wise.

Tabs

Currently, the dashboard has two types of tabs -

Revenue (figure: 4.1)
Service (figure: 4.1)

Tabs are identified by name in visualizations of config API.

Table chart with drill-down

Table chart visualizations have normal material UI data table features like search, sort etc.

In the table response filter key & drillDownChartId has a value that indicates it is a drill-down table.

Cards

Each card header is localized and has an info icon with a tooltip option which displays the header and the description.
The number of cards in rows on the page is driven by the backend. The backend provides a row number to each card where it should be displayed.
The card contains an option icon that contains the image download and image share options.
Image download and share option use id from vizArray in order to differentiate each card on a page.

Download and Share (figure 2.9)

The download has two options - download as an Image or PDF

Upload localization keys:

code: pre-defined key for back-end

message: message contains the value for the key

module: rainmaker-dss

locale: contains locale data

Contact eGov team for more details

Module name: rainmaker-dss

NPM Module Used

Note:: Consider this while pushing new State data - both MDMS state names and codes should be in sync

Where id is state code and name is state name.

If the values are pushed under different names then the existing file is updated accordingly.

Steps to setup DSS in local

Step 1: Run as independent, switch to micro-ui-internals folder

Step 2: Run yarn install and yarn start:dev to start working on DSS in a local setup.

API Call Role Action Mapping

Supporting links

National Dashboard - About & FAQs

About and Purpose page for National Dashboard Enhancement

Overview - About Page

An about the dashboard page that describes the purpose of the dashboard as well as the source of the data is required to be built as per the feedback received from the demos.

Web URL:-

The file location in Digit-Dev:- ../modules/dss/src/pages/About.js

The file location in egov-mdms-data:- ../../pb/dss-dashboard/About.json

code

OUTPUT

Add Content

To add a question we need to mention titleHeader

To add the first point we need to mention define

To add the first sub-points we need to mention definePoints

To add the second point we need to mention subdefine

To add the second sub-points we need to mention subdefinePoints

Remove Content

If we need to remove the content we need to delete it according titleHeader,define,definePoints, subdefine, subdefinePoints

Overview - FAQ Page

To enhance the dashboard and make it more user-friendly, an FAQ page is to be developed so that users can access it from any page for any queries that they may have regarding any acronyms or how to navigate.

The File location in egov-mdms-data:- ../../pb/dss-dashboard/FAQs.json

code

OUTPUT

Add Content

To add a question we need to mention question

To add the First point we need to mention answer, ans

To add the First sub-points we need to mention answer, point

To add the Second point we need to mention subAnswer, ans

To add the Second sub-points we need to mention subAnswer, point

Remove Content

If we need to remove the content we need to delete it according question, answer, subAnswer, ans, point

roleactions.json:- path:- ../../pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

actions-test.json:- path:- ../../../ACCESSCONTROL-ACTIONS-TEST/actions-test.json

DSS UI Flow

Overview

Individual DSS configurations like FSM - DSS configuration is built on the DSS module where configuration and data are received from a set of APIs which can be accessed by users with specific user roles.

Module-wise Role Access To DSS Module

Role - FSM_ADMIN

Module - FSM

API Curl

1curl 'https://qa.digit.org/dashboard-analytics/dashboard/getDashboardConfig/fsm?_=1627404589797' \ 2 -H 'authority: qa.digit.org' \ 3 -H 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"' \ 4 -H 'accept: application/json, text/plain, */*' \ 5 -H 'dnt: 1' \ 6 -H 'sec-ch-ua-mobile: ?0' \ 7 -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36' \ 8 -H 'auth-token: 1bc96a3e-c6c0-4af7-9b97-5cff0c035f98' \ 9 -H 'content-type: application/json;charset=utf-8' \ 10 -H 'sec-fetch-site: same-origin' \ 11 -H 'sec-fetch-mode: cors' \ 12 -H 'sec-fetch-dest: empty' \ 13 -H 'referer: https://qa.digit.org/digit-ui/employee/dss/dashboard/fsm' \ 14 -H 'accept-language: en-US,en;q=0.9,hi;q=0.8' \ 15 --compressed

APIs

Data for each configuration is fetched using {env}/dashboard-analytics/dashboard/getChartV2?_=1627404593531

API CURL -

curl 'https://qa.digit.org/dashboard-analytics/dashboard/getChartV2?_=1627404593531' \
  -H 'authority: qa.digit.org' \
  -H 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"' \
  -H 'accept: application/json, text/plain, */*' \
  -H 'dnt: 1' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36' \
  -H 'content-type: application/json;charset=UTF-8' \
  -H 'origin: https://qa.digit.org' \
  -H 'sec-fetch-site: same-origin' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-dest: empty' \
  -H 'referer: https://qa.digit.org/digit-ui/employee/dss/dashboard/fsm' \
  -H 'accept-language: en-US,en;q=0.9,hi;q=0.8' \
  --data-raw '{"aggregationRequestDto":{"visualizationType":"METRIC","visualizationCode":"fsmTotalrequest","queryType":"","filters":{"tenantId":[]},"moduleLevel":"","aggregationFactors":null,"requestDate":{"startDate":1617215400000,"endDate":1627410599999,"interval":"month","title":"Apr 1, 2021 - Jul 27, 2021"}},"headers":{"tenantId":"pb.amritsar"},"RequestInfo":{"apiId":"Rainmaker","authToken":"1bc96a3e-c6c0-4af7-9b97-5cff0c035f98"}}' \
  --compressed

Each of the charts will have unique data parameters and responses in distinct API calls.

UI Components

Fundamentally DSS has various functionalities including filtering of data, charts and drill-down charts with download PDF, Image and .XLS files. This is achieved by various components utilizing external plugins and internal services

Filters

Filter component in DSS consists of 4 components:-

Date Range

The DateRange component is a styling wrapper around DateRangePicker plugin.

ULB / DDR Filter

Filter on the basis of ULB and DDR (District) is done by selecting single or multiple instances of DDR/ ULB. DDR is an encapsulation of ULBs, and getChart API filters data on the basis of ULB tenants,

Sample request header -

{
  "aggregationRequestDto": {
    "visualizationType": "METRIC",
    "visualizationCode": "fsmTotalrequest",
    "queryType": "",
    "filters": {
      "tenantId": [
        "pb.jalandhar",
        "pb.phagwara"
      ]
    },
    "moduleLevel": "",
    "aggregationFactors": null,
    "requestDate": {
      "startDate": 1617215400000,
      "endDate": 1627410599999,
      "duration": "month",
      "title": "Apr 1, 2021 - Jul 27, 2021"
    }
  },
...

The component in itself uses MultiSelectDropdown component

Denomination

React Component named Switch which uses styled radio inputs.

Generic Chart

The GenericChart is a common wrapper for all charts. It adds the basic styles to all the chart components.

Metric Chart

The MetricChart component is a wrapper component around the MetricChartRow component. MetricChartRow component uses getChart API to fetch data for the “METRIC“ chart type. The MetricData component is a styling component used to format data.

Area Chart

The CustomAreaChart component is used to render line chart types. It can format data based on denomination filter data. It uses the AreaChart component from the recharts package to draw the chart.

Bar Chart

The CustomBarChart component is used to render the performing-metric chart type. It uses the BarChart component from the recharts package to draw the chart.

Horizontal Bar Chart

The CustomHorizontalBarChart component is used to render horizontal bar chart type. It uses the BarChart component from the recharts package to draw the chart.

Pie Chart

The CustomPieChart component is used to render the doughnut chart type. It displays the top 4 categories and aggregates all the other categories into the “Others“ category. It uses the PieChart component from the recharts package to draw the chart.

Tabular Chart

The CustomTable component is used to render table chart types. The insights are calculated by fetching the previous year's data and compared with the current data.

Download Service

The download service is a common service used by all the chart components to facilitate the download/share pdf option. It is handled by using the JSPDF package.

External Plugins

Recharts

JSPDF

HTML2Canvas

XLXS

DateRangePicker

National Dashboard Adaptor Service

Overview

Provides a detailed walk-through of how to set up, configure and deploy Airflow DAGs on the state side to extract data from the Elastic Search server to push to the National Dashboard Adaptor.

Scope

Design and develop an adaptor service which will extract data from the state DIGIT installations and push it onto the National Dashboard instance periodically.

A list of tasks for this has been tracked for the Adaptor

Jira - Dashboard

Adaptor to be deployed on state DIGIT installations
Periodically, the adaptor extracts data and aggregates it from the different DIGIT modules
Posts the data to the National Dashboard for the state
Bookkeeping is done for every adaptor data extract and pushes for audit and debugging
Out of scope: Extraction from non-DIGIT sources

A national dashboard adaptor extracts data from the state DSS at a scheduled time which can be configured and then would ingest in the National Dashboard. The adaptor ingests data at the state/ULB/Ward level for each module on a daily basis. The adapter sends the data in a batch size of 50 to the national dashboard.

Property Tax - National Dashboard

Technical Document

Overview

NDSS has two sides to it. One is the process in which the data is pooled to the ElasticSearch and the other is the way it is fetched, aggregated, computed, transformed and sent across.

As this revolves around a variety of data sets, there is a need for making this configurable. This ensures that the process can be configured easily in case a new scenario is introduced.

This document walks us through the steps on how to define the configurations for DSS analytics for Property Tax module.

Key Concepts

Analytics: A microservice responsible for building, fetching, aggregating and computing the Data on ElasticSearch to a consumable data response. This is later used for visualizations and graphical representations.

Analytics Configurations: Analytics contains multiple configurations. We need to add the changes related to National Dashboard in this dashboard analytics. Dashboard analytics configuration file path: Below is a list of configurations that need to be changed to run the National Dashboard successfully.

Chart API Configuration
Master Dashboard Configuration
Role Dashboard Mappings Configuration

Chart API Configuration: Each visualization has its own properties. Each visualization comes from different data sources (sometimes it is a combination of different data sources). In order to configure each visualization and its properties, we have a Chart API Configuration Document.

In this, Visualization Code, which happens to be the key, has its properties configured as a part of the configuration and is easily changeable.

Sample ChartApiConfiguration.json data for the Property Tax below.

Master Dashboard Configuration: Master Dashboard Configuration is the main configuration which defines the Dashboards to be painted on the screen. It includes all visualizations, their groups, the charts which comes within them and even their dimensions in terms of height and width.

Role Dashboard Mappings Configuration: Master Dashboard Configuration which was explained earlier hold the list of available dashboards.

Given the instance where Role Action Mapping is not maintained in the Application Service, this configuration acts as the Role - Dashboard Mapping Configuration. Each Role is mapped against the Dashboard which they are authorized to see. This was used earlier when the Role Action Mapping of eGov was not integrated. Later, when the Role Action Mapping started controlling the Dashboards to be seen on the client side, this configuration was just used to enable the Dashboards for viewing.

MDMS configuration file path: common-masters/uiCommonConstants.json

roleaction.json

Action test.json:

Property Tax-National DSS contains multiple graphs that represent the PT data. Each graph has its own configuration that describes the chart and its type.

National DSS contains the following charts in Property Tax:

Revenue Tab:

Overview
Total Cumulative Collection
Top 3 States By Performance
Bottom 3 States by Performance
Collection by Usage Type
Key Financial Indicators
- Boundary
- Usage
Tax Heads
- Boundary
- Usage

Service Tab:

Overview
Total Cumulative Properties Assessed
Top 3 Performing States By Completion
Bottom 3 Performing States By Completion
Properties By Usage Type
Properties By Financial Year

Revenue Tab:

Overview: Overview graph contains multiple data information as below in the selected time period.
Collection on: This represents the today’s collection amount.
Total Collection: This represents the total collection amount.
Target Collection: This represents the target collection amount.
Target Achievement: This represents the target achieved in percentage. This is calculated by formula- (Total Collection/Target Collection)*100%

Total Cumulative Collection: This graph contains the Property Tax collection amount information in the monthly base as a cumulative line graph. This will change as per the denomination amount filter selection.

line - this graph/chart is data representation on date histograms or date groupings.

Top 3 Performing States By Completion -This graph represents the States based on the target achieved in bar chart representation with the % of target achieved in descending order.

Bottom 3 States by Performance - This graph represents the States based on the target achieved in bar chart representation with the % of target achieved in ascending order.

Collection by Usage Type - This graph shows the collection amount based on the usage/property type.

Key Financial Indicators

Boundary - This tabular chart representation graph shows multiple W&S information like Target Collection, Total Collection, Total Transactions, Total Assessed Properties and Target Achievement (in %). And this table shows the data at the State level and also has the drill-down chart for each State to ULB and from ULB to ward level data for the same.

xtable type allows adding multiple computed fields with the aggregated fields dynamically added.

To add multiple computed columns, computedFields [] where actionName (IComputedField<T> interface), fields [] names as in existing query key, newField as name to appear for computation must be defined.

Clicking on any State name provides a drill-down view of charts for the specific ULB level data.

Clicking on the ULB navigates users to the wards specific data.

Usage - shows the data in the form of connection type for the given time period. Usage Type, Total Collection, Transactions, Assessed Properties.

Tax Heads

Boundary - This tabular chart representation graph shows multiple PT information like Total Collection, Penalty, Interest etc. And this table shows the data at the State level and also has the drill-down chart for each State to ULB and from ULB to ward level data for the same.

table type allows adding multiple aggregated fields.

Clicking on the State name provides a drill down view of the specific ULB data in the form of charts.

Clicking on the ULB navigates to the specific ward and displays the ward-level data insights.

Usage - shows the data in form of Connection type for the given time period. Usage Type, Total Amount,Tax, Cess, Rebate, Penalty, Interest.

Service Tab

Overview: The overview graph contains multiple data information as below in the selected time period.

Total Applications: This represents the total number of applications.
Total Properties: This represents the total number of properties registered.
Total Properties Assessed: This represents the total Properties Assessed.
Total Assessments: This represents the total Assessment of Properties.
Completion Rate: This represents Total Properties Assessed / Total Properties.

Total Cumulative Properties Assessed: This Graph contains the Assessed Properties information in the monthly base as a cumulative line graph.

line - this graph/chart is data representation on date histograms or date groupings.

Top 3 Performing States By Completion: This graph represents the States based on the Assessed Properties of Total Properties Register in bar chart representation with the % in descending order.

Bottom 3 Performing States By Completion: This graph represents the States based on the Assessed Properties of Total Properties Register in bar chart representation with the % in descending order.

Properties By Usage Type: This circular chart represents the assessed properties as part of connection type like commercial, industrial, residential etc for the given time period.

Properties By Financial Year: This table shows total number of properties which has been registered on the system for the financial years.

Index Properties of National Property Tax - The index that contains data for National-PT is- pt-national-dashboard. The mapping details for this index is given below:

The following table that describes the properties mentioned above:

Postman collection for National Property Tax

Fire NOC - National Dashboard

Technical Doc

Overview

DSS has two sides to it. One is the process in which the data is pooled to ElasticSearch and the other is the way it is fetched, aggregated, computed, transformed and sent across.

As this revolves around a variety of data sets, there is a need for making this configurable. This ensures that the process can be configured easily in case a new scenario is introduced.

This document walks us through the steps on how to define the configurations for DSS state analytics for the Fire NOC module.

Technical Details

Analytics: Microservice responsible for building, fetching, aggregating and computing the data on ElasticSearch to a consumable data response. This is later used for visualizations and graphical representations.

Analytics Configurations: Analytics contains multiple configurations. Add the changes related to fire NOC in this dashboard analytics. Configuration file path: Below is a list of configurations that need to be changed to run the fire NOC data analytics successfully.

Chart API Configuration
Master Dashboard Configuration
Role Dashboard Mappings Configuration

Chart API Configuration: Each visualization has its properties. Each visualization comes from different data sources (Sometimes it is a combination of different data sources). To configure each visualization and its properties, we have a Chart API Configuration Document.

The Visualization Code, which happens to be the key, has its properties configured as a part of the configuration and are easily changeable.

Sample ChartApiConfiguration.json data for the Fire NOC -

Master Dashboard Configuration: Master Dashboard Configuration is the main configuration which defines as which are the Dashboards which are to be painted on the screen.

It includes all the Visualizations, their groups, the charts which come within them and even their dimensions as what should be their height and width.

Role Dashboard Mappings Configuration: Master Dashboard Configuration which was explained earlier holds the list of dashboards that are available.

Given the instance where role action mapping is not maintained in the Application Service, this configuration acts as a role dashboard mapping configuration. In this, each role is mapped against the dashboard that they are authorized to see.

This was used earlier when the role action mapping of eGov was not integrated. Later, when the role action mapping started controlling the dashboards to be seen on the client side, this configuration was just used to enable the dashboards for viewing.

MDMS Configuration to be added: common-masters/uiCommonConstants.json

roleaction.json

Action test.json:

FireNoc-National DSS contains multiple graphs that represent the Fire NOC data. Each graph has its own configuration that describes the chart and its type.

National DSS contains the following charts in Fire NOC:

Fire Noc Page

Overview
Total Cumulative Collection
Total applications vs Provisional NOCs issued vs Actual NOCs issued
Collection by Payment Mode
Total NOCs issued by type
Actual Fire NOCs by usage type
Top 3 Performing States
Bottom 3 Performing States
Service Report

Overview: The overview graph contains multiple data information as below in the selected time period.

Today’s Collection: This represents the sum of revenue collected from the issuance of a Provisional and Actual Fire NOC which is Application fee + NOC Issuance fee
Total Collection: Sum of revenue collected from Fire NOC for the applied date filter
Total Applications: Total number of applications submitted for a new Fire NOC
Provisional NOC Issued: The Provisional NOC is to be obtained to ensure that the proposed constructions meet the fire safety compliant norms
Actual NOCs Issued: The Actual NOC is to be obtained to ensure that the proposed constructions meet the fire safety compliant norms
Avg. days to issue Provisional Fire NOC: Average number of days taken to issue a Provisional NOC
Avg. days to issue Actual Fire NOC: Average number of days taken to issue an actual NOC
SLA Compliance (Actual Fire NOC): % of Actual NOCs issued within SLA
SLA Compliance (Provisional Fire NOC): % of Provisional NOCs issued within SLA

Total Cumulative Collection: This graph contains the Fire NOC collection amount information on a monthly base as a cumulative line graph for each Fire NOC collection separately. This will change as per the denomination amount filter selection.

line - this graph/chart is data representation on date histograms or date groupings.

Total applications vs Provisional NOCs issued vs Actual NOCs issued: This graph contains the Fire NOC showing total applications submitted vs provisional NOCs issued vs actual NOCs issued for a given month collection separately. This changes as per the denomination amount filter selection.

line - this graph/chart is data representation on date histograms or date groupings.

Collection by Payment Mode: This is a pie chart showing the bifurcation of total collections by payment mode (online, cash, card, cheque) which is the sum of revenue collected from Fire NOC for the applied date filter.

Total NOCs issued by type: This is a pie chart showing bifurcation of Total NOCs issued into Provisional and Actual Fire NOCs. The sum of Provisional and Actual Fire NOCs issued.

Actual Fire NOCs by usage typeThe total: This is a pie chart showing a bifurcation of Actual Fire NOCs by usage type. Total number of Fire NOCs issued by the concerned authority.

Top 3 Performing States: This card shows the Top 3 Performing States/ULBs/Wards based on % NOCs issued. The number of Fire NOCs issued / Number of applications depends on whether a user selects 'Provisional' or 'Actual'.

Clicking on Actual shows the % of NOCs issued for Actual Fire NOCs.

Clicking on Provisional shows the % of NOCs issued for Actual Fire NOCs.

Clicking on the Show More option displays information about all states.

Bottom 3 Performing States: This card shows the Bottom 3 Performing States/ULBs/Wards based on % NOCs issued. The Number of Fire NOCs issued / Number of applications depends on whether a user selects 'Provisional' or 'Actual'.

Clicking on Actual shows the % of NOCs issued for Actual Fire NOCs.

Clicking on Provisional shows the % of NOCs issued for Actual Fire NOCs.

Clicking on Show More provides information on all the states.

Service Report: This tabular chart representation graph shows multiple Fire NOC information like Total Collection, Applications Submitted, Provisional Fire NOC issued, New Fire NOC Issued, Average days to issue Provisional NOC, SLA Compliance (Provisional NOC), Average days to issue New NOC, SLA Compliance (New NOC). And this table shows the data at the state level and also has the drill-down chart for each state to ULB and from ULB to the ward level data for the same.

xtable type allows to add multiple computed fields with the aggregated fields dynamically added.

To add multiple computed columns, computedFields [] where actionName (IComputedField<T> interface), fields [] names as in exist in query key, newField as name to appear for computation must be defined.

Clicking on any region name provides drill-down charts representing the specific state data.

Clicking on the ULB navigates to wards under that specific ULB and each ward shows the specific data regarding that ward.

Newly Introduced Properties

isRoundOff: This property is introduced to round off the decimal values. Ex: if the value is 25.43 by using isRoundOff property in the configuration we will get it as 25. if the value is 22.56 round of value will be 23. This can be used for insights configuration as well for overview graphs.

Common Properties Available

Key(eg: fsmTotalrequest): This is the Visualization Code. This key will be referred to in further visualization configurations.

This is the key which will be used by the client application to indicate which visualization is needed for display.

chartName: The name of the Chart which has to be used as a label on the Dashboard. The name of the Chart will be a detailed name.

In this configuration, the Name of the Chart will be the code of Localization which will be used by the Client Side.

queries: Some visualizations are derived from a specific data source. While some others are derived from different data sources and are combined together to get a meaningful representation.

The queries of aggregation which are to be used to fetch out the right data in the right aggregated format are configured here.

queries.module: The module/domain level, on which the query should be applied on. Fire NOC is FIRE NOC.

queries.indexName: The name of the index upon which the query has to be executed is configured here.

queries.aggrQuery: The aggregation query in itself is added here. Based on the Module and the Index name specified, this query is attached to the filter part of the complete search request and then executed against that index

queries.requestQueryMap: Client Request would carry certain fields which are to be filtered. The parameters specified in the Client Request are different from the parameters in each of these indexed documents.

In order to map the parameters of the request to the parameters of the ElasticSearch Document, this mapping is maintained.

queries.dateRefField: Each of these modules has separate indexes. And all of them have their own date fields.

When there is a date filter applied against these visualizations, each of them has to apply it against their own date reference fields.

In order to maintain what is the date field in which index, we have this configured in this configuration parameter.

chartType: As there are different types of visualizations, this field defines what is the type of chart /visualization that this data should be used to represent.

Chart types available are:

metric - this represents the aggregated amount/value for records filter by the aggregate es query

pie - this represents the aggregated data on grouping. This is can be used to represent any line graph, bar graph, pie chart or donuts

line - this graph/chart is data representation on date histograms or date groupings

perform - this chart represents groping data as performance wise.

table - represents a form of plots and value with headers as grouped on and list of its key, values pairs.

xtable - represents a advanced feature of table, it has addition capabilities for dynamic adding header values.

valueType: In any case of data, the values which are sent to plot, might be a percentage, sometimes an amount and sometimes it is just a count.

In order to represent them and differentiate the numbers from amount from percentage, this field is used to indicate the type of value that this Visualization will be sending.

action: Some of the visualizations are not just aggregation on data source. There might be some cases where we have to do a post aggregation computation.

For Example, in the case of Top 3 Performing ULBs, the Target and Total Collection is obtained and then the percentage is calculated. In these kinds of cases, what is the action that has to be performed on that data obtained is defined in this parameter.

documentType: The type of document upon which the query has to be executed is defined here.

drillChart: If there is a drill down on the visualization, then the code of the Drill Down Visualization is added here. This will be used by Client Service to manage drill downs.

aggregationPaths: All the queries will be having Aggregation names in it. In order to fetch the value out of each Aggregation Responses, the name of the aggregation in the query will be an easy bet. These aggregation paths will have the names of Aggregation in it.

insights: It is to show the data with the comparison of last year with arrow symbols, it will show the data in how much % is increased or decreased.

_comment: In order to display information on the “i” symbol of each visualization, Visualization Information is maintained in this field.

Index Properties of National Fire NOC-DSS

The index that contains data for National Fire NOC is - firenoc-services

The mapping for this index is given below

The following is the table that describes the properties mentioned above:

Postman collection for National FireNoc- Dss:

Trade License - National Dashboard

Technical Doc

Overview

NDSS has two sides to it. One is the process in which the data is pooled to the ElasticSearch and the other is the way it is fetched, aggregated, computed, transformed and sent across.

As this revolves around a variety of data sets, there is a need for making this configurable. This ensures that the process can be configured easily in case a new scenario is introduced.

This document walks us through the steps on how to define the configurations for DSS analytics for the Trade License module.

Technical Details

Analytics: Microservice responsible for building, fetching, aggregating and computing the data on ElasticSearch into a consumable data response. This is used for visualizations and graphical representations.

Analytics Configurations: Analytics contains multiple configurations. Add the changes related to OBPS in this dashboard analytics.

Configuration file path:

Below is a list of configurations that need to be changed to run the National Dashboard successfully.

Chart API Configuration
Master Dashboard Configuration
Role Dashboard Mappings Configuration

Chart API Configuration: Each visualization has its own properties. The visualization data is fetched from different sources. In some cases, it is a combination of different data sources. The Chart API configuration document is used to configure each visualization and its properties.

The visualization code is the key whose properties are configured here. These properties are easily changeable.

Below is the sample ChartApiConfiguration.json data for the Trade License.

Master Dashboard Configuration: Master dashboard configuration is the main configuration that defines the dashboards to be painted on the screen. This includes the visualizations, their groups, the charts and the chart dimensions in terms of height and width.

Role Dashboard Mappings Configuration: Master Dashboard Configuration which was explained earlier hold the list of Dashboards which are available.

Given the instance where Role Action Mapping is not maintained in the Application Service, this configuration will act as Role - Dashboard Mapping Configuration

In this, each Role is mapped against the Dashboard which they are authorized to see

This was used earlier when the Role Action Mapping of eGov was not integrated.

Later, when the Role Action Mapping started controlling the Dashboards to be seen on the client side, this configuration was just used to enable the Dashboards for viewing.

MDMS Configuration to be added: common-masters/uiCommonConstants.json

roleaction.json

Action test.json:

Trade License-National DSS contains multiple graphs that represent trade license data. Each graph has its own configuration that describes the chart and its type.

National DSS contains the following charts in Trade License:

Revenue Tab:

Overview
Total Cumulative Collection
Top 3 States By Performance
Bottom 3 States by Performance
Collection by Trade Type
Key Financial Indicators
Tax Heads

Service Tab:

Overview
Total Cumulative Licenses Issued
Top 3 Performing States By Completion
Bottom 3 Performing States By Completion
Trade Licenses by Status
Status Report

Revenue Tab:

Overview: The Overview graph contains multiple data information as below in the selected time period.

Today’s Collection: This represents the day’s collection amount.
Total Collection: This represents the total collection amount.
Target Collection: This represents the target collection amount.
Target Achievement: This represents the target achieved in percentage. This is calculated by the formula - (Total Collection/Target Collection)*100

Total Cumulative Collection: This graph displays the Trade License collection amount information on a monthly base as a cumulative line graph. The graph changes as per the selected denomination amount filter.

line - this graph/chart is data representation on date histograms or date groupings.

Top 3 Performing States By Completion: This graph represents the States based on the Target achieved in bar chart representation with the % of target achieved in descending order.

Bottom 3 States by Performance: This graph represents the States based on the Target achieved in bar chart representation with the % of target achieved in ascending order.

Collection by Trade Type: This graph shows the collection amount based on the trade type.

Key Financial Indicators: This tabular chart representation displays multiple Trade License information like Target Collection, Total Collection, Total Transactions, Total Licenses Issued and Target Achievement (in %). The table shows the data at the State level and also provides the drill-down chart for each State to ULB and from ULB to the ward level data.

xtable type allows adding multiple computed fields with the aggregated fields dynamically added.

To add multiple computed columns, define computedFields [] where actionName (IComputedField<T> interface), fields [] names as existing in query key, newField as name to appear for computation must be defined.

Clicking on any State name provides the drill-down charts and data for that specific ULB.

Clicking on the ULB navigates to the ward-level data for that specific ULB.

Tax Heads: This tabular chart representation graph shows multiple Trade License information like TL Tax, Adhoc Penalty, Adhoc Rebate, Total Amount etc. The table displays the data at the State level and also provides a drill-down chart for each State to ULB and from ULB to ward level data for the same.

table type allows adding multiple aggregated fields.

Clicking on the State name provides the drill-down charts that represent the specific ULB data.

Clicking on the ULB navigates to the ward level data illustration.

Service Tab:

Overview: The Overview graph illustrates multiple data information as below in the selected time period.

Total Applications: This represents the total number of trade license applications.
Total Licenses: This represents the total licenses issued.

Total Cumulative Licenses Issued: This graph displays the licenses issued and total application information on a monthly base as a cumulative line graph.

line - this graph/chart is data representation on date histograms or date groupings.

Top 3 Performing States By Completion: This graph represents the States based on the number of licenses issued within SLA and the number of licenses issued, in bar chart representation with the % in descending order.

Bottom 3 Performing States By Completion: This graph represents the states based on the number of licenses issued within SLA and the number of licenses issued, in bar chart representation with the % in ascending order.

Trade Licenses by Status: This circular chart represents the number of trade licenses according to status.

Status report: This table shows the status-wise breakup of trade licenses by states for the selected year.

If we select a state, the drill down chart for ULBs in that state appears.

Index Properties of National Trade License: The index that contains the data for National-Trade License is- tl-national-dashboard

The mapping for this index is given below:

The table below describes the properties mentioned above:

National Dashboard API Performance Testing and Benchmark

Overview

Since we have around 600 wards in Punjab, we decided to make the national dashboard service robust enough to handle 600 requests simultaneously in a short time( preferably midnight when the employees ingest the day’s data ).

Performance Testing Details

The national dashboard ingest service API underwent extensive stress testing. The service was tested for 25 concurrent threads (users) targeting 100 requests per minute with each request payload containing 30 records (the ingest API is a bulk API). The service passed all the tests with 0 percent error with a throughput of 21 requests per second with a total number of samples being 12671 in 10 minutes which roughly equals 21 requests per second.

The stress test ran with the following configuration and reliably persisted each and every record that was ingested -

National-dashboard-ingest service -

Number of pods- 5
Number of threads for each pod- 25
Heap memory- 750 mb
Producer linger time- 1 ms

National dashboard Kafka pipeline service -

Number of pods- 3
Number of threads for each pod- 10
Heap memory- 512 mb
Producer linger time- 1 ms

National Dashboard: Index Creation Steps

Overview

This document lists the steps to be followed to create national dashboard indexes.

Pre-requisites

Prior Knowledge of ElasticSearch

Index Creation Steps

The steps to be followed to create a property tax index for the national dashboard are exemplified here.

Open Kibana
Create an index using the following query -
1PUT pt-national-dashboard 2{}
Add corresponding field mappings for the created index -

 PUT pt-national-dashboard/_mapping/nss
 {
        "properties" : {
          "assessedPropertiesForUsageCategory" : {
            "type" : "long"
          },
          "assessments" : {
            "type" : "long"
          },
          "cessForUsageCategory" : {
            "type" : "long"
          },
          "createdBy" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "createdTime" : {
            "type" : "long"
          },
          "date" : {
            "type" : "date",
            "format" : "dd-MM-yyyy HH:mm:ss||dd-MM-yyyy||epoch_millis||dd-MM-yyyy'T'HH:mm:ss.SSSZ"
          },
          "financialYear" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "interestForUsageCategory" : {
            "type" : "long"
          },
          "lastModifiedBy" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "lastModifiedTime" : {
            "type" : "long"
          },
          "module" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "penaltyForUsageCategory" : {
            "type" : "long"
          },
          "propertiesRegisteredForFinancialYear" : {
            "type" : "long"
          },
          "propertyTaxForUsageCategory" : {
            "type" : "long"
          },
          "rebateForUsageCategory" : {
            "type" : "long"
          },
          "region" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "state" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "todaysClosedApplications" : {
            "type" : "long"
          },
          "todaysCollectionForUsageCategory" : {
            "type" : "long"
          },
          "todaysTotalApplications" : {
            "type" : "long"
          },
          "transactionsForUsageCategory" : {
            "type" : "long"
          },
          "ulb" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "usageCategory" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "ward" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          }
        }
      }

Fire NOC - National Dashboard

Technical Doc

Overview

DSS has two sides to it. One is the process in which the data is pooled to ElasticSearch and the other is the way it is fetched, aggregated, computed, transformed and sent across.

As this revolves around a variety of data sets, there is a need for making this configurable. This ensures that the process can be configured easily in case a new scenario is introduced.

This document walks us through the steps on how to define the configurations for DSS state analytics for the Fire NOC module.

Technical Details

Chart API Configuration
Master Dashboard Configuration
Role Dashboard Mappings Configuration

The Visualization Code, which happens to be the key, has its properties configured as a part of the configuration and are easily changeable.

Sample ChartApiConfiguration.json data for the Fire NOC -

Master Dashboard Configuration: Master Dashboard Configuration is the main configuration which defines as which are the Dashboards which are to be painted on the screen.

It includes all the Visualizations, their groups, the charts which come within them and even their dimensions as what should be their height and width.

 {
      "name": "NSS_FIRE_NOC_DASHBOARD",
      "id": "national-firenoc",
      "isActive": "",
      "style": "linear",
      "visualizations": [
        {
          "row": 1,
          "name": "NSS_REVENUE",
          "vizArray": [
            {
              "id": 342,
              "name": "NSS_OVERVIEW",
              "dimensions": {
                "height": 350,
                "width": 2
              },
              "vizType": "metric-collection",
              "noUnit": true,
              "isCollapsible": false,
              "charts": [
                {
                  "id": "nssNOCTodaysCollection",
                  "name": "NSS_NOC_TODAYS_COLLECTION",
                  "code": "",
                  "chartType": "metric",
                  "filter": {
                    "title": "TODAY"
                  },
                  "headers": []
                },
                {
                  "id": "nssNOCTotalCollection",
                  "name": "NSS_NOC_TOTAL_COLLECTION",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                },
                {
                  "id": "nssNOCTotalApplications",
                  "name": "NSS_NOC_TOTAL_APPLICATIONS",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                },
                {
                  "id": "nssNOCProvisionalIssued",
                  "name": "NSS_NOC_PROVISIONAL_ISSUED",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                },
                {
                  "id": "nssNOCActualIssued",
                  "name": "NSS_NOC_ACTUAL_ISSUED",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                },
                {
                  "id": "nssNOCAverageDaysToIssueProvisional",
                  "name": "NSS_NOC_AVERAGE_DAYS_TO_ISSUE_PROVISIONAL",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                },
                {
                  "id": "nssNOCSLAComplianceProvisional",
                  "name": "NSS_NOC_SLA_COMPLIANCE_PROVISIONAL",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                },
                {
                  "id": "nssNOCAverageDaysToIssueActual",
                  "name": "NSS_NOC_AVERAGE_DAYS_TO_ISSUE_ACTUAL",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                },
                {
                  "id": "nssNOCSLAComplianceActual",
                  "name": "NSS_NOC_SLA_COMPLIANCE_ACTUAL",
                  "code": "",
                  "chartType": "metric",
                  "filter": "",
                  "headers": []
                }
              ]
            },
            {
              "id": 342,
              "name": "NSS_NOC_TOTAL_CUMULATIVE_COLLECTION",
              "dimensions": {
                "height": 350,
                "width": 7
              },
              "vizType": "chart",
              "label": "",
              "noUnit": true,
              "isCollapsible": false,
              "charts": [
                {
                  "id": "nssNOCCumulativeCollection",
                  "name": "Monthly",
                  "code": "",
                  "chartType": "line",
                  "filter": "",
                  "headers": []
                }
              ]
            }
          ]
        },
        {
          "row": 2,
          "name": "NSS_REVENUE",
          "vizArray": [
          	{
              "id": 343,
              "name": "NSS_APPLICATION_VS_PROVISIONAL_VS_ACTUAL",
              "dimensions": {
                "height": 190,
                "width": 10
              },
              "vizType": "chart",
              "isCollapsible": false,
              "label": "",
              "charts": [
                {
                  "id": "nssNOCApplicationVsProvisionalVsActual",
                  "name": "Monthly",
                  "code": "",
                  "chartType": "line",
                  "filter": "",
                  "headers": []
                }
              ]
            },
            {
              "id": 210,
              "name": "NSS_NOC_COLLECTION_BY_PAYMENT_MODE",
              "dimensions": {
                "height": 250,
                "width": 4
              },
              "vizType": "chart",
              "label": "",
              "noUnit": false,
              "isCollapsible": false,
              "charts": [
                {
                  "id": "nssNocCollectionByPaymentMode",
                  "name": "NSS_NOC_COLLECTION_BY_PAYMENT_MODE",
                  "code": "",
                  "chartType": "donut",
                  "filter": "",
                  "headers": []
                }
              ]
            },
            {
              "id": 211,
              "name": "NSS_TOTAL_NOC_ISSUED_TYPE",
              "dimensions": {
                "height": 250,
                "width": 4
              },
              "vizType": "chart",
              "noUnit": false,
              "isCollapsible": false,
              "charts": [
                {
                  "id": "nssTotalNocIssuedByType",
                  "name": "NSS_TOTAL_NOC_ISSUED_TYPE",
                  "code": "",
                  "chartType": "donut",
                  "filter": "",
                  "headers": []
                }
              ]
            }
          ]
        },
        {
          "row": 3,
          "name": "NSS_REVENUE",
          "vizArray": [
            {
              "id": 212,
              "name": "NSS_ACTUAL_NOC_ISSUED_USAGETYPE",
              "dimensions": {
                "height": 250,
                "width": 4
              },
              "vizType": "chart",
              "noUnit": false,
              "isCollapsible": false,
              "charts": [
                {
                  "id": "nssActualNocIssuedByUsageType",
                  "name": "NSS_ACTUAL_NOC_ISSUED_USAGETYPE",
                  "code": "",
                  "chartType": "donut",
                  "filter": "",
                  "headers": []
                }
              ]
            },
            {
              "id": 221,
              "name": "NSS_NOC_TOP_3_PERFORMING_STATES",
              "dimensions": {
                "height": 250,
                "width": 4
              },
              "vizType": "performing-metric",
              "isCollapsible": false,
              "label": "",
              "charts": [
                {
                  "id": "nssNOCTopPerformingStatesActual",
                  "name": "NSS_NOC_TOP_3_PERFORMING_STATES_ACTUAL",
                  "code": "",
                  "chartType": "bar",
                  "filter": "",
                  "headers": [],
                  "tabName": "Actual"
                },
                {
                  "id": "nssNOCTopPerformingStatesProvisional",
                  "name": "NSS_NOC_TOP_3_PERFORMING_STATES_PROVISIONAL",
                  "code": "",
                  "chartType": "bar",
                  "filter": "",
                  "headers": [],
                  "tabName": "Provisional"
                }
              ]
            },
            {
              "id": 222,
              "name": "NSS_NOC_BOTTOM_3_PERFORMING_STATES",
              "dimensions": {
                "height": 250,
                "width": 4
              },
              "vizType": "performing-metric",
              "isCollapsible": false,
              "charts": [
                {
                  "id": "nssNOCBottomPerformingStatesActual",
                  "name": "NSS_NOC_BOTTOM_3_PERFORMING_STATES_ACTUAL",
                  "code": "",
                  "chartType": "bar",
                  "filter": "",
                  "headers": [],
                  "tabName": "Actual"
                },
                {
                  "id": "nssNOCBottomPerformingStatesProvisional",
                  "name": "NSS_NOC_BOTTOM_3_PERFORMING_STATES_PROVISIONAL",
                  "code": "",
                  "chartType": "bar",
                  "filter": "",
                  "headers": [],
                  "tabName": "Provisional"
                }
              ]
            }
          ]
        },
        {
          "row": 4,
          "name": "NSS_REVENUE",
          "vizArray": [
            {
              "id": 231,
              "name": "Service Report",
              "dimensions": {
                "height": 350,
                "width": 12
              },
              "vizType": "chart",
              "noUnit": false,
              "isCollapsible": false,
              "charts": [
                {
                  "id": "nssNOCServiceReportByState",
                  "name": "NSS_NOC_SERVICE_REPORT_STATE",
                  "code": "",
                  "chartType": "table",
                  "filter": "",
                  "headers": [],
                  "tabName": "State"
                },
                {
                  "id": "nssNOCServiceReportByDepartment",
                  "name": "NSS_NOC_SERVICE_REPORT_DEPARTMENT",
                  "code": "",
                  "chartType": "table",
                  "filter": "",
                  "headers": [],
                  "tabName": "Department"
                }
              ]
            }
          ]
        } 
      ]
    }

Role Dashboard Mappings Configuration: Master Dashboard Configuration which was explained earlier holds the list of dashboards that are available.

{
  "_comment": "Holds mapping for each role with and its associated dashboards",
  "roles" : [
    {
      "_comment":"This role is super role which can access all the available dashboards: [other/new roles are suppose to be added]",
      "roleId": 6,
      "roleName" : "Admin",
      "isSuper" : "",
      "orgId": "",
      "dashboards": [
        {
          "name": "National Fire Noc",
          "id": "national-firenoc"
        }
      ]
    }

  ]
}

MDMS Configuration to be added: common-masters/uiCommonConstants.json

"national-firenoc":{
                  "routePath":"/dashboard/national-firenoc",
                  "isOrigin":true
               }
               }

roleaction.json

{
      "rolecode": "STADMIN",
      "actionid": {{PlaceHolder1}},
      "actioncode": "",
      "tenantId": "pb"
    },
    
    {
      "rolecode": "STADMIN",
      "actionid": {{PlaceHolder2}},
      "actioncode": "",
      "tenantId": "pb"
    },
     {
      "rolecode": "EMPLOYEE",
      "actionid": {{PlaceHolder2}},
      "actioncode": "",
      "tenantId": "pb"
    },  
     {
      "rolecode": "UC_EMP",
      "actionid": {{PlaceHolder2}},
      "actioncode": "",
      "tenantId": "pb"
    },

Action test.json:

{
      "id": {{PlaceHolder1}},
      "name": "NSS Dashboard Config obps",
      "url": "/dashboard-analytics/dashboard/getDashboardConfig/national-firenoc",
      "parentModule": "",
      "displayName": "NSS",
      "orderNumber": 0,
      "enabled": false,
      "serviceCode": "NSS",
      "code": "null",
      "path": ""
},
{
      "id": {{PlaceHolder2}},
      "name": "National Dashboard Fire Noc",
      "url": "url",
      "displayName": "National Fire Noc",
      "orderNumber": 4,
      "parentModule": "ndss-dashboard",
      "enabled": true,
      "serviceCode": "NDSS",
      "code": "null",
      "path": "NatDashboard.FireNoc",
      "navigationURL": "integration/dss/national-firenoc",
      "leftIcon": "places:business-center",
      "rightIcon": ""
}

FireNoc-National DSS contains multiple graphs that represent the Fire NOC data. Each graph has its own configuration that describes the chart and its type.

National DSS contains the following charts in Fire NOC:

Fire Noc Page

Overview
Total Cumulative Collection
Total applications vs Provisional NOCs issued vs Actual NOCs issued
Collection by Payment Mode
Total NOCs issued by type
Actual Fire NOCs by usage type
Top 3 Performing States
Bottom 3 Performing States
Service Report

Overview: The overview graph contains multiple data information as below in the selected time period.

Today’s Collection: This represents the sum of revenue collected from the issuance of a Provisional and Actual Fire NOC which is Application fee + NOC Issuance fee
Total Collection: Sum of revenue collected from Fire NOC for the applied date filter
Total Applications: Total number of applications submitted for a new Fire NOC
Provisional NOC Issued: The Provisional NOC is to be obtained to ensure that the proposed constructions meet the fire safety compliant norms
Actual NOCs Issued: The Actual NOC is to be obtained to ensure that the proposed constructions meet the fire safety compliant norms
Avg. days to issue Provisional Fire NOC: Average number of days taken to issue a Provisional NOC
Avg. days to issue Actual Fire NOC: Average number of days taken to issue an actual NOC
SLA Compliance (Actual Fire NOC): % of Actual NOCs issued within SLA
SLA Compliance (Provisional Fire NOC): % of Provisional NOCs issued within SLA