...
Top 3 Performing States : This card will show the Top 3 Performing States/ULBs/Wards based on % NOCs issued. Number of Fire NOCs issued / Number of applications depending on whether a user selects 'Provisional' or 'Actual'.
On click of Actual it shows the % of NOCs issued for Actual FireNocs.
On click of Provisional it shows the % of NOCs issued for Actual FireNocs.
...
Bottom 3 Performing States : This card will show the Bottom 3 Performing States/ULBs/Wards based on % NOCs issued. Number of Fire NOCs issued / Number of applications depending on whether a user selects 'Provisional' or 'Actual'.
On click of Actual it shows the % of NOCs issued for Actual FireNocs.
On click of Provisional it shows the % of NOCs issued for Actual FireNocs.
...
Service Report : This tabular chart representation graph shows multiple Fire NOC information like Total Collection, Applications Submitted, Provisional FireNoc issued, New FireNOC 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 in state level and also has the drill down chart for each state to ulb and from ulb to ward level data for the same.
...
On click of the ULB will navigate to wards under that specific ULB and each ward shows the specific data regarding that ward.
Newly introduced property:
isRoundOff: This property is introduced to round off the decimal values. Ex: if the value is 25.43 by using isRoundOff property in configuration we will get it as 25. if value is 22.56 round of value will be 23.
This can be used for insights configuration as well for overview graph.
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 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 FIRENOC.
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 have 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 FireNoc- Dss:
The index that contains data for National-FireNoc is- firenoc-national-dashboard
The mapping for this index is:
| Code Block |
|---|
{
"properties": {
"tenantId": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"date": {
"type": "date",
"format": "dd-MM-yyyy HH:mm:ss||dd-MM-yyyy||epoch_millis"
},
"module": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"ulb": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"region": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"todaysApplicationsForApplicationType": {
"type": "long"
},
"todaysApplicationsForDepartment": {
"type": "long"
},
"todaysCollectionForDepartment": {
"type": "long"
},
"provisionalNOCIssuedForDepartment": {
"type": "long"
},
"actualNOCIssuedForDepartment": {
"type": "long"
},
"avgDaysToIssueProvisionalNOCForDepartment": {
"type": "long"
},
"slaComplianceActualForDepartment": {
"type": "long"
},
"avgDaysToIssueActualNOCForDepartment": {
"type": "long"
},
"actualNOCIssuedByDeptForDepartment": {
"type": "long"
},
"nocIssuedTodayForType": {
"type": "long"
},
"todaysCollectionForPaymentMode": {
"type": "long"
},
"state": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"ward": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"applicationType": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"department": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"type": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
},
"paymentMode": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 256
}
}
}
}
} |
The following is the table that describes the properties mentioned above:
Attributes | Definition | Breakup |
ulb | The district or region for which the data is ingested | Nil |
state | The ULB name for which the data is ingested | Nil |
ward | The ward for which the data is ingested | Nil |
transactions | Number of transactions related to WS/SW module on a given date | Nil |
connectionsCreated | Number of connections related to WS/SW module on a given date | Breakup by channel type and connection type has to be provided |
todaysCollection | Total collection related to WS/SW module on a given date | Breakup by usage type, channel type and tax head has to be provided |
waterConnections | new connections created on the given date | Breakup by meter type,usage and channel |
sewerageConnections | new sewreage connections created on the given date | Breakup by usage and channel |
pendingConnections | pending connections on the given date | Breakup by duration |
slaCompliance | Percentage of complaints that are resolved within SLA till the given date. | Nil |
todaysTotalApplications | # of Applications created on the given date | Nil |
todaysClosedApplications | # of Applications closed on the given date | Nil |
todaysCompletedApplicationsWithinSLA | # of Applications closed on the given date within SLA | Nil |
Postman collection for National FireNoc- Dss: