Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Fire NoC provides a digital interface to apply for pre-construction (provisional) and post-construction (new) NoC, pay NoC fees, track the status of the application, generate payment receipts, NoC certificates, multilevel workflow as well as generate reports for collection, employee performance etc. It can be used by stakeholders like a citizen, employee (document verifier, field inspectors, approver, ULB administrators) to accomplish specific tasks.
The high-level feature set based on the user type is listed below.
Citizens
Apply for Pre-construction and Post-construction NoC
Submit required documents online
Track application status
View applicable fees and calculation breakup details
Pay online and offline through multiple channels
Download payment receipt and an application confirmation form
Download QR code-enabled No Objection Certificate/ Rejection Certificate
Counter Employee
Apply for Pre-construction and Post-construction NoC on behalf of citizens
View calculation breakup details
Apply Ad-hoc rebate/penalty
Collect NoC fees
Generate and print payment receipt/ application confirmation form
Download and print multiple copies - employee and citizen copy
Search and download QR code-enabled No Objection Certificate/ Rejection Certificate
Document Verifier
Verify attached documents
Forward or reject applications
Send back application for clarification
Refer applications for an opinion to other employees
Provide comments or remarks
Field Inspector
Verify and inspect the details given in NoC forms physically
Forward or reject applications
Send back applications for clarification
Refer applications for an opinion to other employees
Provide comments or remarks
Upload inspection reports and photos if required
Approver
Approve or Reject Application
Send back application for clarification
Refer applications for an opinion to other employees
Provide comments or remarks
Access collection reports and employee performance reports
ULB Admin
Access collection reports and employee performance reports
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
After the building usage types are identified, the next activity is to identify the building sub usage types.
Buildings types can be further classified into various subcategories to go into the granular level of their usage details. The National Building Code of India (NBC) also classifies the building's usage type into the sub usage types which can be seen in the attachment.
1
BU01
BSU01
Hotel
A4
Hotel
2
BU01
BSU02
Apartment
A5
Apartment House
The data given in the above table is sample data.
1
Building Usage Type Code
Reference
64
Yes
2
Sub Type Code
Alphameric
64
Yes
The code is given to the building sub usage type by the Fire Station. Eg: BSU01 for Hotel, BSU02 for Apartment Houses
3
Building Sub Usage Type
Text
256
Yes
Name of subcategories within each building usage type as per the fire station. Eg: Hotel, Apartment Houses
4
Sub Divison (as per NBC)
Alphameric
64
Yes
The code is given to the building sub usage type as per NBC. Eg: Subdivision A4, A5
5
Building Sub Usage Type (as per NBC)
Text
256
Yes
Name of subcategories within each building usage type as per NBC. Eg: Hotel, Apartment House
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify and add all the different sub usage types for each building group that are being catered by the fire station in the Building Sub Usage Type column.
Next, give each building Sub Usage type a unique code and enter the code in the Sub Usage Type Code column, next to the Building Sub Usage type.
Map the data filled in the building sub usage type column to the building sub usage type and Subdivision as per the national building code.
Record the appropriate subdivision and building sub usage type from NBC in the Subdivision (as per NBC) and Building Sub Usage Type (as per NBC) respectively.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
1
Make sure that each and every point in this reference list has been taken care of
This checklist covers the activities which are specific to the entity.
1
BU01: Residential
BU02: Educational
2
Building Sub Usage Type Codes that are defined by the Fire Station should be alphanumeric and unique
BSU01: Hotel
BSU02: Apartment
3
Building Sub Usage Type should not contain any special characters
Hotel : [Allowed]
#Hotel! : [Not allowed]
This page provides configuration details for Fire NOC master data templates
The Fire No-Objection Certificate (NOC) application, developed on the eGov-DIGIT platform, makes the process of obtaining a Fire NOC easy, smooth, and transparent. It eliminates the current manual process by automating and streamlining it, thus providing a better citizen service experience with the Urban Local Body (ULB) and Fire station employees.
Features offered to the citizens-
Apply for provisional or new fire NOC or renew existing Fire NOC.
Upload all the relevant documents required for the certificate.
Make payment for the Fire NOC using the online payment gateway.
Receive notifications and alerts by SMS, whenever the status of the application changes.
Download Fire NOC
Features offered to the Employees-
Flexible role-based workflow.
Configurable fee calculation mechanism.
Dashboard with application statistics.
Search applications using configurable parameters.
Receipt Register
Application Status
The codes are given to the building usage type in the
The Building Usage Type Code should be similar to the ones defined in the
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Apply for fire NOC, pay service fees, ensure compliance with fire safety guidelines, and lots more
The Fire No-Objection Certificate (NOC) application, developed on the eGov-DIGIT platform, makes the process of obtaining a Fire NOC easy, smooth, and transparent. It eliminates the current manual process by automating and streamlining it, thus providing a better citizen service experience with the Urban Local Body (ULB) and Fire station employees.
Features offered to the citizens-
Apply for provisional or new fire NOC or renew existing Fire NOC
Upload all the relevant documents required for the certificate
Make payment for the Fire NOC using the online payment gateway
Receive notifications and alerts by SMS, whenever the status of the application changes
Download Fire NOC
Features offered to the Employees-
Flexible role-based workflow
Configurable fee calculation mechanism
Dashboard with application statistics
Search applications using configurable parameters
This section contains all docs and information required to understand the Fire NOC module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the Fire NOC module.
Functional Specifications
NOC Roadmap
Fire NOC User Manual
Product Brochure
NOC Workflows
Master Data Configuration Template
Fire NOC Service Configuration
Implementation Handbook
Demo Script
Navigation Tips
Click on the embedded links within the content to browse topic details
Use the Contents links available on the right side of the screen to move to a specific heading
Find the list of Related Docs links at the bottom of each page to browse through additional product details
Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on Fire NOC module deployment.
#147/J, 1st floor, 10th Cross, 12th Main, 3rd Block, Koramangala, Bangalore 560034
+91 80 4125 5708
contact@digit.org
After the building usage and sub usage ontology has been defined for all the Firestations, the next step is to collect the Fire NOC fee that the citizens have to pay to obtain the certificate.
The Fire NOC fee is dependent on the following parameters:
Fire Station
Building Usage type
Building Sub usage type
Fire NOC type
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the Fire station codes of all the fire stations that are there in the Fire Station master, in the ‘Fire Station Code Column’.
Next, enter the Building usage types codes and building sub usage type codes that being catered by the fire station, next to the Fire Station Code.
Identify the fees that the fire stations are charging to issuing a new, provisional, or renewed Fire NOC for every building usage and sub usage combination.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
We are using re-indexing to get all the data to the respective indexer. We have 2 steps for this. First is to run the connector from the playground, which is followed by legacyindexer service call from the indexer service, which internally calls the respective plain search service to get the data and to send it to the respective indexer.
Access to kubectl of the environment targetted
Postman scripts
Plain search APIs in the respective services
fire noc-services reindexing steps
Configure the fire noc indexer with the configKey as LEGACYINDEX
with the new topic name in the respective indexer yaml
Connect to playground pod.
Delete the kafka connector if already exists with the kafka connection, using below command through playground pod.
Run below kafka connector curl from playground pod:
port forward to egov-indexer pod and run below curl throw postman.
Delete the kafka connection after all the data has been re-indexed by following below command through playground pod.
Alias firenoc-services-enriched as water-services through kibana server.
NOW your firenoc-services index is update with the data of firenoc till now in the system.
In almost all the states fire stations serve both the urban as well as the rural areas, therefore we need to prepare the masters for both urban areas as well as the rural areas being served in the state.
The data given in the above table is sample data.
Urban Area
Rural Area
Urban Areas
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the districts where fire services are provided and enter their names in the District Name column.
Give each district a unique code and enter the code in the District Code column, next to the District Name.
Identify all the ULBs within each district where fire services are provided and enter their name in the ULB Name column next to its District Name.
Give each ULB a unique code and enter the code in the ULB Code column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
Rural Areas
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify the districts where fire services are provided and enter their names in the District Name column.
Give each district a unique code and enter the code in the District Code column, next to the District Name.
Identify all the Sub District within each district where fire services are provided and enter their name in the Sub District Name column next to its District Name.
Give each Sub District a unique code and enter the code in the Sub District Code column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
After we have created the fire station master, the next step would be to map the Districts, Sub-Districts, and ULBs with the fire stations. The two points that are very important to note here are:
All the ULBs in the state may not have a fire department.
Usually, only the larger ULBs in the state have a fire department that caters to that ULB at the same time to all the surrounding smaller ULBs and rural areas as well.
Note: Data given in the above table is sample data.
Urban Area
Rural Area
Urban Area - Fire Mapping
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the district codes of all the districts where fire services are provided, in the ‘District Code Column’.
Next, enter the ULB codes of all the ULBs within a particular district where the fire services are provided in the 'ULB Code Column'.
Identify the fire stations that are serving each District - ULB combination and enter their name in the Fire Station column along with its code in the Fire Station Code.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
Rural Area - Fire Mapping
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Enter the district codes of all the districts where fire services are provided, in the ‘District Code Column’.
Next, enter the sub-district codes of all the sub-district within a particular district where the fire services are provided in the 'Sub District Code Column'.
Identify the fire stations that are serving each District - Sub District combination and enter their name in the Fire Station column along with its code in the Fire Station Code.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
The first step is to identify all the fire stations within the state. It is important to note that all the ULBs may not have a fire department. Generally, the bigger ULBs of the state have a fire department that caters to that ULB at the same time to all the surrounding smaller ULBs and rural areas as well.
The data given in the above table is sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the fire stations operating in the state and enter their names in the Fire Station Name column
Next, give each fire station a unique code and enter that code in the Fire Station Code column.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
Buildings can be classified into various categories on the basis of their usage. Different fire stations can have different ontology for building usage type but in order to provide citizens and businesses a uniform experience, it is important that the building usage types ontology is standardized at the state level.
For this purpose, the states can also use the National Building Code of India (NBC), a comprehensive building code, which is a national instrument providing guidelines for regulating building construction activities across the country.
The data given in the above table is sample data.
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
Identify all the different types of buildings on the basis of their usage that are being catered by the fire station in their area and start filling them in the Building Usage Type column.
Next, give each building usage type a unique code and enter the code in the Building Usage Type Code column, next to the Building usage type.
Map the data filled in the building usage types column to the building usage type and building groups as per the national building code.
Record the appropriate group and building type from NBC in the Building Group (as per NBC) and Building Usage Type (as per NBC) respectively.
Verify the data once again by going through the checklist and making sure that each and every point mentioned in the checklist is covered.
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
This checklist covers all the activities which are common across the entities.
This checklist covers the activities which are specific to the entity.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by is licensed under a .
All content on this page by is licensed under a .
All content on this page by is licensed under a .
All content on this page by is licensed under a .
All content on this page by is licensed under a .
New
Provisional
Renew
1
FS01
BU01
BSU01
1000
200
800
2
FS02
BU01
BSU02
2000
1000
2000
1
Fire Station Code
Reference
64
Yes
The code given to each Fire station in the Fire Station masters
2
Building Usage Code
Reference
64
Yes
The code given to each Fire station in the Fire Usage Type Master
3
Building Sub Usage Code
Reference
64
Yes
The code given to each Fire station in the Fire Sub Usage Type Master
4
Fire NOC Fee
Integer
6
Yes
The amount that will be charged for each Fire NOC type. For Eg: 2000 for new, 0 for Provisional and 1000 for renew
1
Make sure that each and every point in this reference list has been taken care of
1
Fire station codes, Building Usage code, and Sub usage Codes have to be similar to the codes entered in their respective masters
2
The Fire NOC fee should be an integer, without having any alphabet or symbol preceding or succeeding it
2000: [Allowed]
Rs. 2000 : [Not allowed]
2000 Rs. : [Not allowed]
1
DC01
Amritsar
ULB01
Amritsar
2
DC01
Amritsar
ULB02
Ajnala
1
DC02
Patiala
SDC01
Jhabal
2
DC02
Patiala
SDC02
Patran
1
District Code
Alphameric
64
Yes
The code is given to the district by the state team. Eg: DC01 for Amritsar, DC02 Patiala.
2
District Name
Text
256
Yes
Name of the district Eg: Amritsar, Patiala
3
ULB Code
Text
256
Yes
The code is given to the district by the state team. Eg: ULB01 for Amritsar, ULB02 Ajnala
4
ULB Name
Alphameric
64
Yes
Name of the ULB Eg: Amritsar, Ajnala
1
District Code
Alphameric
64
Yes
The code is given to the district by the state team. Eg: DC01 for Amritsar, DC02 Patiala
2
District Name
Text
256
Yes
Name of the district Eg: Amritsar, Patiala
3
Sub-district Code
Text
256
Yes
The code is given to the subdistrict by the state team. Eg: SDC01 for Jhabal, SDC02 Patran
4
Sub-district Name
Alphameric
64
Yes
Name of the sub-district Eg: Jhabal, Patran
1
Make sure that each and every point in this reference list has been taken care of.
1
District Codes, Sub District Codes, and ULB Codes should be alphanumeric and Unique.
ULB01: Amritsar
SDC01: Jhabal
2
District Name, Sub District Name, and ULB Name should not contain any special characters.
Amritsar : [Allowed]
#Amritsar! : [Not allowed]
1
DC01
ULB01
FS02
Amritsar
2
DC01
ULB02
FS02
Amritsar
1
DC02
SDC01
FS01
Patiala
2
DC02
SDC02
FS01
Patiala
1
District Code
Reference
64
Yes
The code given to each district in the Area served masters
2
ULB Code
Reference
64
Yes
The code given to each district in the Area served masters
3
Fire Station Code
Reference
64
Yes
The code given to each Fire station in the Fire Station masters
4
Fire Station Name
Reference
256
Yes
The Fire Stations listed in the Fire Station masters
1
District Code
Reference
64
Yes
The code given to each district in the Area served masters
2
Sub District Code
Reference
64
Yes
The code given to each sub-district in the Area served masters
3
Fire Station Code
Reference
64
Yes
The code is given to each Fire station in the Fire Station masters
4
Fire Station Name
Reference
256
Yes
The Fire Stations listed in the Fire Station masters
1
Make sure that each and every point in this reference list has been taken care of
1
District Codes, Sub-district Codes, and ULB codes have to be similar to the codes entered in the Area Master
2
The Fire Station Name and the Fire station Code should be similar to the name and codes entered in the Fire Station Master
1
FS01
Patiala
2
FS02
Amritsar
1
Fire Station Code
Alphameric
64
Yes
The code is given to the fire station by the state team. Eg: FS01 For Patiala Fire station, FS02 for Amritsar Fire station
2
Fire Station Name
Text
256
Yes
Name of the fire station. Eg: Patiala, Amritsar
1
Make sure that each and every point in this reference list has been taken care of
1
Fire Station Codes that are defined by the state team should be alphanumeric and Unique
FS01: Amritsar
FS02: Jalandhar
2
Fire station Name should not contain any special characters
Amritsar : [Allowed]
#Amritsar! : [Not allowed]
1
BU01
Residential
Group A
Residential
2
BU02
Educational Institute
Group B
Educational
1
Building Usage Type Code
Alphameric
64
Yes
The code is given to the building usage type by the Fire Station. Eg: BU01 for Residential, BU02 for educational institute
2
Building Usage Type
Text
256
Yes
Name of building usage type by the Fire Station. Eg: Residential, Educational Institute
3
Building Group (as per NBC)
Text
256
Yes
The code is given to the building usage type as per NBC. Eg: Group A, Group B
4
Building Usage Type (as per NBC)
Text
256
Yes
Name of building usage type as per NBC. Eg: Residential, Educational
1
Make sure that each and every point in this reference list has been taken care of
1
Building Usage Type Codes that are defined by the Fire Station should be alphanumeric and Unique
BU01: Residential
BU02: Educational Institute
2
Building Usage Type should not contain any special characters
Residential : [Allowed]
#Residential! : [Not allowed]
Fire-Noc calculator service is used to calculate the fire noc charges for the building based on the billing slab defined in the system. This service allows an employee with SUPERUSER role to create the billing slab with different combination of the height of the building, built_-_up area, plot size, number of floors etc.
Before you proceed with the configuration, make sure the following pre-requisites are met -
Prior knowledge of JavaScript.
Prior knowledge of Node.js platform.
Kafka server is up and running
egov-persister service is running and has firenoc-calculator-persister config path added in it
PSQL server is running and database is created to store firenoc application data
Following services should be up and running:
egov-persister
egov-mdms
firenoc-services
billing-service
An employee with SUPERUSER role can create, update billing slab(s)
ULB Employee with NOC_CEMP, NOC_DOC_VERIFIER, NOC_FIELD_INSPECTOR, NOC_APPROVER, EMPLOYEE can search billing slab(s)
firenoc-services internally call firenoc-calculator to generate demand.
Deploy the latest version of firenoc-services and firenoc-calculator.
Add firenoc-calculator-persister.yml file in config folder in git and add that path in persister . (The file path is to be added in environment yaml file in param called persist-yml-path )
Firenoc Calculator makes calls to egov-mdms-service to fetch required master files. These are significant in validations of application.
Fire-NOC masters
Description
This master file contains the details about which unit of measurement is use for a particular building type.
This master file contains state level constants and their values.
This master file contains list of unit of measurements for firenoc
This master file contains the list of state level constants and their values..
firenoc-calculator will be integrated with firenoc-services. firenoc-services internally invoke the firenoc-calculator service to calculate and generate demand for the charges.
Firenoc calculator application is used to calculate the fire noc charges for the building based on the different billing slabs in the DB that's why the calculation and demand generation logic will be separate out from firenoc services. So in future, if calculation logic needs to modify then changes can be carried out for each implementation without modifying the Firenoc services.
Firenoc application to call /firenoc-calculator/v1/_calculate to calculate and generate the demand for the Firenoc application
/firenoc-calculator/v1/_getbill this API updates demand with time based penalty if applicable and generates bill for the given criteria.
ULB Employee can create billing slab calling /firenoc-calculator/billingslab/_create
ULB Employee can update billing slab calling /firenoc-calculator/billingslab/_update
ULB Employee can search billing slab calling /firenoc-calculator/billingslab/_search
Title
Link
API Swagger Contract
Fire Noc Service Document
Title
Link
firenoc-calculator/billingslab/_create
firenoc-calculator/billingslab/_search
firenoc-calculator/billingslab/_update
firenoc-calculator/v1/_calculate
firenoc-calculator/v1/_getbill
(Note: All the API’s are in the same postman collection therefore same link is added in each row)
__
__
Service configuration
The main objective of the Fire-NOC module is to provide a No Objection Certificate indicating that the building is designed as per fire safety norms and regulations.
Before you proceed with the documentation, make sure the following pre-requisites are met -
Prior knowledge of JavaScript.
Prior knowledge of Node.js platform.
Kafka server is up and running
JSONPath for filtering required data from json objects.
Prior Knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
egov-persister service is running and has firenoc-services persister config path added in it
PSQL server is running and database is created
Prior knowledge of eGov-mdms service, eGov-persister, eGov-user, eGov-location, eGov-localization, eGov-idgen
Used for No Objection Certificate generations indicating that the building is designed as per fire safety norms and regulations.
Generate application number and fire noc number
Support workflow
Provide notification on various status changes for an application
Add mdms configs required for firenoc service and restart mdms service.
Deploy the latest version of firenoc-services service.
Add firenoc-services persister yaml path in persister configuration and restart persister service.
Add Role-Action mapping for APIs.
Create businessService (workflow configuration) according to firenoc registration.
Following are the properties in application.properties file in trade firenoc-service which are configurable.
EGOV_APPLICATION_FORMATE
PB-FN-[cy:yyyy-MM-dd]-[SEQ_EG_TL_APL]
The format of the firenoc application number
EGOV_CIRTIFICATE_FORMATE
PB-FN-[cy:yyyy-MM-dd]-[SEQ_EG_PT_LN]
The format of the firenoc certificate number
EGOV_DEFAULT_STATE_ID
pb
Variable store the default value of state tenantid
EGOV_FN_DEFAULT_LIMIT
100
Max number of records to be returned
KAFKA_TOPICS_FIRENOC_CREATE
save-fn-firenoc
The name of kafka topic on which create request is published
KAFKA_TOPICS_FIRENOC_UPDATE
update-fn-firenoc
The name of kafka topic on which update request is published
KAFKA_TOPICS_FIRENOC_WORKFLOW
update-fn-workflow
The name of kafka topic on which status update request is published
ACTION_PAY
PAY
This is workflow action for making payment against the application
SENDBACK
SENDBACK
This is workflow action for sending application to the previous state of the workflow.
SENDBACKTOCITIZEN
SENDBACKTOCITIZEN
This is a workflow action for sending application to the citizen for correction.
MDMS Configuration
Firenoc service makes calls to egov-mdms-service to fetch required masters. These are significant in the validation of the application.
This master contains the list of application type.
This master contains the details about which unit of measurement is use for a particular building type.
This master contains the list of firestation present in city.
This master contains the list of property type.
This master contains the list of minimum charges of each application type.
Create businessService (workflow configuration) using the __/businessservice/_create. Following is the product configuration for firenoc service
Persister Config
https://github.com/egovernments/configs/blob/DEV/egov-persister/firenoc_persiter.yaml
Id Gen Config
BasePath /firenoc-services/v1/[API endpoint]
Method
a) _create
Create API call is called with INITIATED action to create a new application. In this API call, we validate the request body(using ajv module for contract-specific validation and explicit checking for user-related validation checks), enrich audit details, generate application no using idgen, persist data using persister and return response.
Allowed user roles: NOC_CEMP, CITIZEN
b) _update
Once the application is created it can be updated by citizens or employees while taking action on the application
Allowed user roles: NOC_CEMP, CITIZEN, NOC_DOC_VERIFIER, NOC_FIELD_INSPECTOR, NOC_APPROVER
c) _search
The search API call is used to search for applications. If a search call is being made by CITIZEN then only his application would be fetched by applying other search filters. For employee search based on search filter will return data.
Allowed user roles: NOC_CEMP, CITIZEN, NOC_DOC_VERIFIER, NOC_FIELD_INSPECTOR, NOC_APPROVER, EMPLOYEE
The Fire-Noc service is used to provide a No Objection Certificate indicating that the building is designed as per fire safety norms and regulations.
Provide backend support for the No Objection Certificate registration process for a different building.
SMS notifications on application status changes.
Supports workflow which is configurable
To integrate, the host of firenoc-services service should be overwritten in the helm chart.
firenoc-services/v1/_create should be added as the create endpoint for creating the fire noc application in the system.
firenoc-services/v1/_search should be added as the search endpoint. This method handles all requests to search existing records depending on different search criteria.
firenoc-services/v1/_update should be added as the update endpoint. This method is used to update fields in existing records or to update the status of the application based on workflow.
Title
Link
API Swagger Documentation
Firer Noc Calculator Service
Title
Link
firenoc-services/v1/_create
firenoc-services/v1/_search
firenoc-services/v1/_update
(Note: All the API’s are in the same postman collection therefore same link is added in each row)
__
__
An illustrative guide to using the Fire NOC module
The Fire NOC module allows citizens to make an application for Fire NoC and pay fire NoC fees. The module makes the process of obtaining a Fire NOC easy, smooth, and transparent. It eliminates the current manual process by automating and streamlining it, thus providing a better citizen service experience with the Urban Local Body (ULB) and Fire station employees.
The module supports the following key functions -
Apply for no objection certificate through mobile, web or counter
Apply for Provisional (pre-construction) or New (post-construction) fire NoC
Apply for a single building or multiple buildings owned by the applicant in the same compound
Review application before submission
Pay NoC fees online
Track application status
Download and Print QR code-enabled application confirmation form, payment receipts NoC certificate
Refer to the table below to understand the different user roles and the scope of action linked to each role. The applicable user roles and action items can vary from one State to another. DIGIT customizes the workflows to suit the requirements defined at the State level.
User Role
Scope of Action
Role Description
Citizen
Apply for Fire NOC
Review applications
Pay NoC fees online
Track application status
Download or print NOC certificates, payment receipts
Individuals and society groups/communities
Counter Employee
Apply for Fire NOC
Collect fees
ULB employees at the counter to assist citizen
Document Verifier (DV)
Verify and forward
Send Back
Edit Application
Employees responsible for verifying the supporting documents submitted by applicants
Field Inspector (FI)
Verify and forward
Send Back
Reject
Edit
Employees responsible for physical verification of the information provided by the applicant
Approver
Approve
Send Back
Reject
Cancel
An employee who has the final authority to approve or reject applicants
Citizens
Counter Employee (CE)
Document Verifier (DV)
Field Inspector (FI)
Approver
This section guides you through the details of using the Fire NOC module for each role. Click on the relevant role below to learn more about how to use the module.
Users can view all the applications assigned to them in the employee inbox. And it provides multiple filters and search options to filter the applications.
NOC Inbox uses InboxComposer React HOC to create the Inbox through various child components, for both mobile and desktop components.
The API used to fetch applications in the inbox
NOCAccess function to view NOC Inbox
Use the MDMS (available as blue hyperlinks) for selecting OBPS application type, service type, risk type with business service and status filter.
Config for risk type definition
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
The application overview page shows the details of the application selected and the action that a specific user is allowed to take on that application.
Documents required for NOC approval are gathered from DocumentTypeMapping MDMS.
Common documents that are required are fetched from DocumentType config from MDMS.
Forward application with the uploaded NOC certificate to forward the application to concerned authorities for approval.
Reject application to reject the application.
For multiple uploading of documents, we have used MultiUploadWrapper which encapsulates API calls and abstracts the whole process providing the fileData and fileStoreIds.
Learn how to apply for provisional or New NOC and pay NOC fees
Citizens represent individuals, communities, or business entities who are the system end-users. The Fire NOC module enables citizens to apply for no-objection certificates from the local fire station. The applicants can also make the service fees online, track the status of their applications, download applications, and print payment receipts.
The citizen role can -
Apply for Fire NOC
View application status
Pay service fees
Download/Print applications and payment receipts
The Apply option allows citizens to fill in and submit the application for Fire NOC.
To apply
Navigate to and click on the Fire Noc card on the Citizen Services home page panel.
Click on the Apply button to initiate an application for a Fire NOC.
The system displays the list of documents required to submit with the NOC application. Click on the Print button to print this list or make a note of the required documents.
Click on the Apply button to proceed with the application.
Select the applicable NOC Type. Select New to apply for post-construction NOC. In case New NOC Type is selected, provide the Provisional Fire NOC Number. The application form is auto-filled with the details fetched from the Provisional Fire NOC.
Select Provisional to apply for pre-construction NOC.
Select Single Building or Multiple Buildings options to indicate the No. of Buildings in the Property Details panel.
Enter the property details such as Building Name, Building Usage Type as per NBC, Building Usage Subtype as per NBC, No. of Floors (Excluding Basement, Including Ground Floor), No. of Basements, Plot Size (in Sq meters), Ground Floor Built-up area (in Sq Meters), and Height of Building from Ground Level (in meters).
Enter the Property ID. Click on the search icon in case the property details are registered in the Property Tax module to fetch the linked property details. Skip this field if the property is not registered.
Select the applicable City. Enter the Plot/Survey No., Building/Colony Name, Street Name, Mohalla, and the Pincode details. Click on the map icon to pinpoint the property location on the map.
Select the Applicable Fire Station from the drop-down list. The application will be issued by the selected Fire Station. Click on the Next Step button to proceed to the next section of the application.
Select the applicable Applicant Type in the Applicant Details panel to indicate if the application is raised by an individual, or a government institution, or a private institution. Now, select the relevant Type of Applicant - Subtype. For instance, individual applicants may constitute of single owners or multiple owners. Similar sub-categorization is available in the drop-down list depending on the selected Applicant Type.
Enter the applicant Mobile No., Name, Gender, Date of Birth, Email, Father/Husband Name, PAN No., and Correspondence Address in the Applicant Details panel.
Select the applicable Special Applicant Category option if the applicant belongs to any of the defined categories. Select None of the Above in case the applicant does not belong to any specific category.
Click on the Next Step button to proceed with the application.
The Application No. is generated and visible on the page. Scroll down the application to upload the Required Documents.
Click on the Upload File button to begin uploading. Click on the Next Step button once all the requested documents are uploaded.
The Fee Details panel displays the total amount that has to be paid by the applicant towards NOC Fees.
Scroll down to review the filled in application details. Click on the Edit icon on the page in case any modification is required.
Click on the Submit button once the application is reviewed.
The acknowledgement screen confirms the application is submitted successfully. Click on the Download or Print button to download or print a copy of the application.
Click on the Proceed to Payment button to make the NOC fee payment.
Click on the Go To Home button to navigate back to the home page.
Click on My Applications on the home page to view application status details or to make the payment towards Fire NOC Fees.
The page displays your submitted applications along with the application current status. Click on the View Details button to view application details and to make the payment.
The Task Status panel displays the current status of the application. Click on the View History button to view status details.
Click on the Take Action and then click on the Pay button to proceed with the payment.
The application page displays the Consumer Code generated for the applicant. Review the Fee Details and breakdown available on the page. Click on the Make Payment button to proceed with the payment.
Enter the Paid By, Payer Name, and Payer Mobile No. in the Payer Details panel. If the Paid By is the Owner, the Payer Name and Mobile No. details are auto-populated from the applicant details.
The payment success acknowledgement screen confirms the payment along with the Payment Receipt No. Click on the Download or Print button to download or print the payment receipt.
Technical Doc
DSS has two sides to it. One is the process in which the data is pooled into 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. So that, tomorrow, given a new scenario is introduced, then it is just a configuration away from getting the newly introduced scenario involved in this flow of the process.
This document explains the steps on how to define the configurations for the analytics side Of DSS for FireNoc.
What is analytics?
Analytics: Micro Service which is responsible for building, fetching, aggregating and computing the Data on ElasticSearch to a consumable Data Response. Which shall be later used for visualizations and graphical representations.
Analytics Configurations: Analytics contains multiple configurations. we need to add the changes related to firenoc in this dashboard-analytics. File location : configs/egov-dss-dashboards/dashboard-analytics at qa · egovernments/configs Below is a list of configurations that need to be changed to run firenoc successfully.
Chart API Configuration
Master Dashboard Configuration
Role Dashboard Mappings 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 are easily changeable.
Here is the sample ChartApiConfiguration.json data for the FireNoc.
Click here to check the complete configuration
Master Dashboard Configuration is the main configuration which defines the dashboards 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.
Click here for the complete configuration
Master Dashboard Configuration which was explained earlier holds 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.
Click here to check the configuration
MDMS Configuration to be added:common-masters/uiCommonConstants.json
Click here to check the complete configuration
roleaction.json
Click here to check the complete configuration
Action test.json:
Click here to check the complete configuration
FireNoc-State DSS Consists of multiple graphs which represent the data of FireNoc. Each graph has its own configuration which will describe the chart and its type.
State DSS consists of following charts in FireNoc:
FireNoc 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 FireNOC.
Provisional NOCs 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 basis 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 will change 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 will be 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 will be a pie chart showing the bifurcation of Total NOCs issued into Provisional and Actual Fire NOCs. Sum of Provisional and Actual Fire NOCs issued.
Actual Fire NOCs by usage type: This will be a pie chart showing a bifurcation of Actual Fire NOCs by usage type. The total number of Fire NOCs issued by the concerned authority.
Top 3 Performing States: This card will show 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'.
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.
On click of Show More, it shows the information of all the states.
Bottom 3 Performing States: This card will show 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'.
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.
On click of Show More, it shows the information of all the states.
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 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 the addition of 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 a drill down to the specific state data.
Clicking on the ULB navigates to the wards under that specific ULB and each ward shows the specific data for that ward.
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.
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 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.
metric - this represents the aggregated amount/value for records filtered by the aggregate 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 performance-wise.
table - represents a form of plots and values with headers as grouped on and a list of its key, values pairs.
xtable - represents an advanced feature of the table, it has addition capabilities for dynamic adding header values.
valueType : Instance of data, the values which are sent for plotting, might be a percentage, sometimes an amount and sometimes it is just a count.
In order to represent them and differentiate the numbers from the amount from the 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 aggregations of data sources. There might be some cases where we have to do a post-aggregation computation.
For Example, in the case of the Top 3 Performing ULBs, the Target and Total Collection are obtained and then the percentage is calculated. In these kinds of cases, the action that has to be performed on the 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 them. In order to fetch the value out of each Aggregation Response, the name of the aggregation in the query will be an easy bet. These aggregation paths will have the names of Aggregation in them.
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.
The index that contains data for State-FireNoc is- firenoc-services
The mapping for this index is:
(Note: All the APIs are in the same postman collection therefore the same link is added in each row)
This section illustrates the steps for different employee user roles at the ULB level
Counter Employees are ULB employees responsible for helping citizens apply for fire NOC or pay the NOC fees at the counter. The Fire NoC module provides the Counter Employees with the scope to create new NOC applications on behalf of the citizens, view application status, and accept NOC fee payment.
The Counter Employees can -
Create and submit new application
Make NOC fees payment
The Create New Application option allows counter employees to fill in and submit the NOC application form on behalf of the citizen.
To create new application
Log in to the employee portal and click on the Fire NOC card on the home page.
Click on the New Application button available on the top right corner of the page.
Follow the same steps as outlined for the Citizens in the Apply for Fire NOC section to fill in and submit the application.
Counter Employees can check the application status of the citizen.
To check application status
Enter the applicable search parameter in the Search Fire NOC Application panel.
For instance, select Application Status parameter as Pending for Payment to view all applications pending for payment. Click on the Search button. The system displays the search results filtered by the selected parameter. Click on the Application No hyperlink to open and view the application details.
Click on the Reset button to clear the search filters.
The Document Verifier or DV is responsible for verifying the documents uploaded by the applicants and checking the accuracy, completeness and authenticity of the documents.
DV can -
Forward applications
Reject applications
Refer applications
To verify and forward the applications
Log in to the portal with the DV credentials. Click on the Fire NoC card on the home page.
Enter the relevant search criteria to fetch the applications Pending for Document Verification. Alternatively, users can also view the applications queued for document verification in their employee Inbox.
Click on the Application No hyperlink to view the application details.
Scroll down the application to find the documents uploaded by the applicant. Click on the View button available for each document. This opens the document attachment. Review each document.
Scroll down and click on the Take Action button. Click on the Forward button if the documents are fine. Select the Field Inspector or Assignee to whom the application will be forwarded. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Verify and Forward button. The application is forwarded to the Field Inspector or selected Assignee.
Click on the Reject button in case the documents are not satisfactory or fail to comply with the requirements. Enter any Comments as required in context to the documents or application. Click on the Upload File button to upload any supporting documents. Click on the Reject button. The application is rejected.
The DVs can refer the applications to other employees for their opinion on the application. The refer option enables the DV to resolve any complexities or doubts linked to the application.
To refer applications
Click on the Refer button. Select the employee or Assignee to whom the application will be forwarded for their inputs and opinion. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Refer for Opinion button. The application is forwarded to the selected Assignee for their opinion.
Field Inspector or FI is responsible for inspecting and verifying the field details and compliance with the fire NOC requirements onsite. If the requirements are found satisfactory the application is forwarded for approval, else it is sent back with the FI’s comments.
The FIs can -
Forward applications
Reject applications
Sendback applications
Refer applications
To verify and forward the applications
Log in to the portal with the FI credentials. Click on the Fire NoC card on the home page.
Enter the relevant search criteria to fetch the applications Pending for Field Inspection. Alternatively, users can also view the applications queued for field inspection in their employee Inbox.
Click on the Application No hyperlink to view the application details.
Scroll down the application to review the details filled in by the applicant. Click on the Take Action button. Click on the Forward button in case onsite inspection findings meet the Fire NOC guidelines.
Select the Assignee to whom the application will be forwarded for final approval. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Verify and Forward button. The application is forwarded to the selected Assignee.
Click on the Reject button in case the documents are not satisfactory or fail to comply with the requirements. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Reject button. The application is rejected.
Click on the Sendback button in case the application details require re-verification. The applications are sent back to the document verifier for further action.
Select the Assignee to whom the application will be forwarded for re-verification. Enter any Comments as required in context to the documents or application. Click on the Upload File button to upload any supporting documents. Click on the Sendback button. The application is sent back to the selected assignee for further action.
The FIs can refer the applications to other employees for their opinion on the application. The refer option enables the FIs to resolve any complexities or doubts linked to the application.
To refer applications
Click on the Refer button. Select the employee or Assignee to whom the application will be forwarded for their inputs and opinion. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Refer for Opinion button. The application is forwarded to the selected Assignee for their opinion.
Approver is responsible for the final approval of the Fire NoC application in case the application details comply with the fire NOC requirements. In case of any non-compliance or inaccuracies the application is rejected.
The approver can
Approve applications
Reject applications
Sendback applications
Refer applications
To approve applications
Log in to the portal with the approver credentials. Click on the Fire NoC card on the home page.
Enter the relevant search criteria to fetch the applications Pending for Approval. Alternatively, users can also view the applications queued for approval in their employee Inbox.
Click on the Application No hyperlink to view the application details.
Scroll down the application to review the details filled in by the applicant. Click on the Take Action button. Click on the Approve button in case the application meets the Fire NOC guidelines.
Select the employee or Assignee Name who will issue the Fire NoC. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Approve button. The application is approved.
Click on the Reject button in case the documents are not satisfactory or fail to comply with the requirements. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Reject button. The application is rejected.
Click on the Sendback button in case the application details require re-verification. The applications are sent back to the document verifier or field inspector for further action.
Select the Assignee to whom the application will be forwarded for re-verification. Enter any Comments as required in context to the documents, field inspection or application. Click on the Upload File button to upload any supporting documents. Click on the Sendback button. The application is sent back to the selected assignee for further action.
The approver can refer the applications to other employees for their opinion on the application. The refer option enables the approvers to resolve any complexities or doubts linked to the application.
To refer applications
Click on the Refer button. Select the employee or Assignee to whom the application will be forwarded for their inputs and opinion. Enter any Comments as required in context to the documents or application.
Click on the Upload File button to upload any supporting documents. Click on the Refer for Opinion button. The application is forwarded to the selected Assignee for their opinion.
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
__All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
All content on this page by is licensed under a .