BPA NOC (No Objection Certificate) flow and configuration
Introduction
NOC (No Objection Certificate) is one of the major process required in BPA application flow. NOC’s decided based on the declared area, type of building, the height of the building, occupancy, etc. No objection certificates required at different stages (from the initial plan submission to occupancy application stage) from the various concerned authorities. NOC ‘s are either directly submitted along with the application by a citizen or internally submitted by the department to other departments. Each department has its own format and set of documents required to submit NOC. Currently in a few ULB’s the official will send this communication to other departments in the standard format.
The current system will give the option to setup NOC integration
With manual submission ( Citizen will upload NOC’s)
Give the option for the external department to login with the particular(dedicated) user to check the NOC’s in the current system.
Integrate with third party system. Here third party API's to call and pass the required parameters.
Functionality
The following departments NOC required, eg:
Fire Services
Airport Authority
National Monument Authority
Irrigation
Pollution control board
Railway
Defense
The additional data required by NOC departments are collected as MIS data and pushed to NOC departments. The departments may process it and update back with below information,
Status with values “Approved“,”Rejected”
Remarks about the application and its status
NOC certificate
As a part of ease of doing business, the scheduler will run to check if the concerned department has approved the submitted NOC within specified days, if concerned NOC is not approved then it will be marked as “Deemed Approved”. SLA defined at each department level will be used for deemed approval consideration. Also configurated to decide whether deemed approval required for particular NOC.
NOC Configurations and set up
Table name : egbpa_master_nocconfiguration
INTERGRATION_TYPE | INTEGRATION_INITIATION | SLA/DEEMED_APPROVED | ||
|---|---|---|---|---|
MANUAL | In this case citizen is going to get the NOC directly from respective departments and upload during OBPS application submission. | MANUAL | In this case, there will be a button called 'Initiate' and ULB officials are allowed to initiate NOC application initiation at any level but before the final approval authority. | The SLA in days. Once NOC is initiated and with the SLA days OBPS is not going to get any status then OBPS is going to make that NOC as deemed approved. Each department wise SLA will be configured. |
INTERNAL | In this case, OBPS is going to give department the provision to login into OBPS system and verify and approve/reject the application. | AUTO | In this case, the NOC application initiation will happen automatically at the time of OBPS application submission. | |
THIRD_PARTY | In this case, the OBPS is going to push the data to third party system using provided APIs. |
| ||
NOC Integration
INTEGRATION_TYPE | INTEGRATION_INITIATION | ACTION |
MANUAL | MANUAL | The citizen is going to get the NOC directly from respective departments and upload during OBPS application submission. |
MANUAL | AUTO | The citizen is going to get the NOC directly from respective departments and upload during OBPS application submission. |
INTERNAL | MANUAL | ULB officials are allowed to initiate NOC application at any level but before the final approval authority and departments have the provision to login to the OBPS system to approve/reject the application. |
INTERNAL | AUTO | NOC application will happen automatically at the time of application submission and departments have the provision to login to the OBPS system to approve/reject the application. |
THIRD_PARTY | MANUAL | ULB officials are allowed to initiate a NOC application to the third party. |
THIRD_PARTY | AUTO | NOC application will be pushed to the third party during application submission. |
Sequence Diagram
