DIGIT-Online Building Permission System (OBPS) enables local government to bring in transparency, accountability and time-bound service for the public. With DIGIT-OBPS, professionals like architects, engineers, supervisors can seek permission for construction of a building from any Urban Local Bodies/District Town and Country Planning/Centre for Municipal Administration with a speedy, hassle-free and user-friendly procedure, online.

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

Introduction

The Fee Structure masters list contains the fee details applicable for processing specific services. All fee-related information collected by the authorities during the course of building plan approval is maintained in this masters.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify the combination of attributes for with the fee is defined and then fill into the given template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Introduction

This module enables Architects / Engineers / Supervisors /Town Planners etc. to register Online. Provision to migrate already registered Architects/ Engineers / Supervisors details in the system with current status and validity of registration. Provision to renew the registration.

1. Centralized Registration: Provide a single interface for the registration of all architects (across the state), who intend to do a transaction with the ULBs.

2. Online Application for Registration: Identify the applicant with reference to a unique ID. Capture the following minimum information of the applicant with appropriate validations.

   1. Unique ID

   2. Name

   3. Address

   4. Corporate Information

   5. Certificate from Council of Architecture/ Other authorities

   6. Educational Qualification

3. This module will also consist of the following:-

   1. Facility for uploading of attachments as required by ULB for establishing identity and past experience etc.

   2. Enable online submission of registration fee.

   3. Assigning a unique application number to each applicant.

   4. Enable tracking the status of the application.

Functional Scope

The OBPS product features can be broadly classified as the following modules:

1. Online registration of Architects/ Engineers / Supervisors etc.

2. Online Real Time Scrutiny of Drawing/Plan

3. Submission of Application and uploading Documents

4. Application Process by the Department

5. Online Payment

6. Certificate

7. Notice

8. General requirements

9. Module 1: Online registration of Architects/ Engineers / Supervisors etc.

10. Approval of Applications: Enable the Competent Authority to approve/reject the applications for registration; based on a workflow system and business rules. Communication of successful registration/ rejection to the applicant through an e-mail alert & SMS.

11. Renewal of Registrations: Enable the Competent Authority to renew the applications for registration according to workflow/business rules. Communication of successful renewal will be sent to the applicant through an e-mail alert & SMS.

12. Search: Enable authorized officials to search the database for list of registered architects based on the ‘search’ criteria such as - line of business, turnover, past experience or as decided by ULB.

13. Help: Provide an online handbook and user manual for registration. Provide FAQs on the registration process. ULB official will provide help desk assistance for resolving architects queries on registration process.

14. Module 2: Online Real Time Scrutiny of Drawing/Plan

15. The Module enables the Architect/Engineer to submit the Drawing in Drawing Interchange Format(DXF) format from any Open Source CAD tools of their choice. The condition for the following are:

    1. The drawing should adhere to the Standards stipulated.

    2. The Standards will be provided to the Architect in the native format (DXF) .

16. The Module enables the Architect/Engineer to submit the Application for various Services as listed above along with required supporting documents. Under the current provision, the document checklist will aid the Architect/Engineer.

    1. The scrutiny process is online realtime and the Architect/Engineer will get the detailed Scrutiny report within minutes of submitting the Plan.

    2. Scrutiny reports will list the Bye-laws and sub-clauses with the approved values against the extracted values.

    3. Based on the extracted value range validation will be done by the system.

    4. Only on clearance of all the Rules Scrutinised the Report will reflect ACCEPTED.

    5. On Accepted Report a unique number of the Scrutiny will be generated

17. Scrutiny Parameters for all types of building meant for different usage; as per building bye laws and approved master plan will be taken into scrutiny. The major Plan provisions are as under :

    1. Plot area / shape

    2. Road width details

    3. MOS (Marginal open space)

    4. Ground coverage

    5. FAR (Floor area ratio)

    6. Building height

    7. Use of building (Floor wise including mixed use in floors)

    8. Parking provision

    9. Amenities

    10. Components of building

    11. Services Evaluation

    12. Firefighting requirement

    13. Green building norms

    14. Rain Water Harvesting

    15. Water supply

    16. Water treatment

    17. Solid waste management provisions

    18. NOC required on the basis of drawing details

18. Module 3: Submission and processing of Application

19. The entire process from the time of submission of drawing to scrutiny completion is automatic without any human intervention and instantaneous.

    1. If the Scrutiny report REJECT the drawing the Report will have the details of the clauses in which it was rejected and also the values of the parameters.

    2. The Architect/Engineer can correct the drawing and can resubmit the drawing till he gets the approval.

    3. Only on approval the unique reference number for the Scrutiny Report will be generated.

    4. Only with this number the Submission of Application can be initiated.

20. The OBPS handles the Plan Scrutiny in Online Real time mode and there is no need for any wait time, once the Plan is drawn. Scrutiny gets completed in less than a minute..

21. From the Plan submitted by the Architect the System will generate all the relevant plan in PDF format automatically. These are the set of Plans which will be issued to the end user with certification on successful completion of the Application Process.

22. The Application can be filled and required documents can be uploaded by the Architect once he has the Plan Scrutiny Reference number.

23. On Submission the Citizen need to validate and self certify the Application.

24. Module -4: Application Process by the Department

25. Workflow is configurable as per the requirements and will be done during the Customisation phase of the Project

26. All approvals will be electronically signed (e-sign) with QR code

27. The application captures all relevant details for all internal and external agencies; relevant data needs to be forwarded to corresponding agencies for issuing NOCs.

28. SLA on NOC is also validated by the System. If the required date is passed without a reply from the NOC department the NOC will be taken as Deemed approved.

29. In addition a single window mechanism is also built into the system. This feature can be used by Departments which do not have the IT system for their process in full.

30. Provision for entering onsite inspection details and geo-tagged images (document upload facility) of the Site Inspection.

31. The product has for the staff and the management for viewing the completed and pending tasks / works / applications.

32. The product has features for Online single window system, and integrations with all internal and external agencies required to provide applicable NOCs/approvals (Fire Services, Water and Sewerage Department, Discoms, AAI, NMA, Forest, Labour, Factory Directorate)

33. A Statewide Dashboard is also available which can be used by State Administrators to see the flow of applications and the pendency or exceptions.

34. The product offers Security on User Authentication with Role based access

35. The product will generate various MIS reports as per requirements of the Departments from time to time. MIS reports based on the payment received, dues position, plans passed, pending proposals, delayed approvals be generated as per Department requirement.

36. The Product has well-defined inspection report format at various levels to guide the inspectors which is also configurable.

37. The Product incorporates digital signature (e-sign) for approval of application at different levels in the application system, Building permission letter, approved drawing, notices, letters, completion cum occupancy certificates etc.

38. Product has well defined service levels and the escalation matrix to officials regarding time limit for processing an application automatically in the system.

39. The Product after the Citizen validates the application the system will schedule the Document Verification visit date. This date can be rescheduled by both the parties once.

40. SMS/Email Alerts enabled in the Product

    1. Document Verification Meeting

    2. Field Verification

    3. Fee Computed and Demand Generated

    4. Plan Permit Approved and Digitally Signed

41. The Checklist for the Document Verification will be filled up by the officials on the Document Verification meeting. In the system the the Checklist is configurable.

42. The Product offers provision to incorporate the changes of building by-laws as intimated by the department in the application within time frame.

    1. Product has the feature to capture the history of changes and based on the original application submission date the relevant rules will be taken into account for scrutiny.

43. The Product has the feature of provisioning ther Revoking/Cancelling of Building Permission.

44. On completion of the Document Verification the applicable NOC Departments will be addressed by the System for NOC.

45. Field Verification Schedule will be assigned by the System with reschedule option for both the parties once.

46. The officials can do the Field Verification, update the report in a checklist format and forward for approval

47. Module-5: Online Fee Payments

48. The solution is integrated with the payment gateway for Online Payments and facilitate for Fee collection, Fee calculation, refund calculation and generate online fee receipts based on the submitted Building plan.

49. Upon approval of the report and NOC clearances the Fees are computed automatically by the system.

50. The Fee computation uses the Plan Parameters and the applicable laws and rules of the State which are configurable.

51. The Plans in PDF will be generated by the System with QR Code without any manual intervention.

52. Citizen/Architect can pay the Fees Online

53. Upon payment of Fees Plan Permit Approval process will be initiated and approved with Digital Signature. The Permit has been incorporated with QR Code.

54. The Fees can be collected under various heads of accounts and the Reports for the collections against the Heads of Accounts will be generated. This will enable the user to account the collections accordingly.

55. Module-6: Certificate(s)

56. The product has provision to generate certificates with e-Sign/ digital signature and QR code which can be downloaded by the applicant.

57. Module-7: Notice(s)

58. The notices, acknowledgment letters, approval letters, deviation or the rejection letters will be system generated with e-sign.

59. Every communication sent/received from/by an applicant will be received online only and reflected in the case as well as in the reports which can be used in court cases & for any other purpose.

60. Module-8: General requirements

61. The software tracks delays in approval steps and maintain an audit log of the approval process steps.

    1. System generates an alert against each application when it nears the time limit for disposing it.

62. The solution allows extraction of system logs to excel/pdf formats for internal analysis of cases.

63. The product have provisions where in providing basic parameters like certificate no., name, area etc. would generate basic information about approved certificate and hence would enable easy third party verification.

64. The Checklist, FAQ, User guide with video should be provided for end users.

65. The product provision to get month wise approved/ rejected/ pending application and status of pending approval.

Below mentioned table mention the functionality of the offered product as per the recommendations under the guidelines mentioned under the Ease of Doing Business(EODB) guidelines of 2019.

Introduction

No objection certificates (NOC) are certifications or permissions acquired from various bodies like Airport authority, monument authority, etc before any construction activities actually take place.

To acquire a building permit, an applicant needs to acquire NOC from the concerned authorities. Add the specific authorities at the State/ULB level in the NOC Departments master list for automated processing of NOCs. Refer to the for details on State/ULB specific NOC requirements.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify all the departments, services and the approach on integration and then fill into the given template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Introduction

Service-wise documents list tells about the documents required for processing of listed services. Citizens can view the checklist based on the selected service. States/ULBs can configure the list of supporting documents required for each service.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify the documents which are needed to avail the services and fill into the given template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Introduction

The list of services in the OBPS module refers to the various types of services offered to citizens or end-users. The Data Table below contains an indicative list of services and details required to configure the building plan approval module.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify the services provided by the DIGIT OBPAS system and enter them into the template with other configurable parameters given in the template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

About OBPAS

Manual processes related to scrutiny, approval, or rejection of building construction or renovation plans is a time-consuming process for both citizens and employees. The DIGIT OBPAS module automates the entire building plan approval process right from enabling online submission of plans, documents to initiating verification and final approval of the plan. Citizens can now track their plan approval or inspection status, pay fees online, download and print the Permit Order and Occupancy Certificate online. The module streamlines the building plan approval system with configurable workflows for effective management through different phases of approval.

Key Features

• Centralized login page for citizens, officials and stakeholders

• Citizen functionalities

• Online application submission - new construction

• Occupancy certificate request

• Field inspection report capture

• Pay fee online and generate permit orders online

• Inspection of applications and online status

• Configurable workflow

• Auto fee calculation

• Online and offline payment collection

• Rejection process

• Revocation process

• Configurable functionalities

Section Overview

This section contains all docs and information required to understand the OBPAS module, its key features, functional scope, and configuration details. Click on the links below to learn more about deploying, configuring, customizing, and using the OBPAS module.

• Functional Specifications

• OBPAS Roadmap

• OBPAS User Manual

• Product Brochure

• OBPAS Workflows

• Master Data Configuration Template

• OBPAS Service Configuration

• Implementation Handbook

• Demo Script

Contact Us

Reach out to us through any of the below-mentioned contact channels for any assistance or additional information on OBPAS module deployment.

Introduction

Manual processes related to scrutiny, approval, or rejection of building construction or renovation plans is a time-consuming process for both citizens and employees. The DIGIT OBPAS module automates the entire building plan approval process right from enabling online submission of plans, documents to initiating verification and final approval of the plan. Citizens can now track their plan approval or inspection status, pay fees online, download and print the Permit Order and Occupancy Certificate online. The module streamlines the building plan approval system with configurable workflows for effective management through different phases of approval.

Module Features

• Centralized login page for citizen, officials and stakeholders

• Citizen functionalities

• Online application submission - New construction

• Occupancy certificate request

• Field Inspection Report Capture

• Pay fee online and generate permit order online

• Inspection of applications and online status

• Configurable workflow

• Auto fee calculation

• Online and offline payment collection

• Rejection process

• Revocation process

• Configurable functionalities

Module Ontology

State Level

1. List of services

2. Occupancy

3. Sub Occupancy

4. Usage

5. List of documents for each service

6. Inspection checklist

7. List of stakeholder types

8. Town planning schemes

9. List of NOC departments

ULB Level

1. Fee structure

Module Reports

None as of now.

Introduction to BPA

The Building Plan Approval or BPA module allows stakeholders to submit building plans for approval by the concerned ULB departments. The construction or renovation of buildings is regulated by the Municipal Body in India. One must get permission from ULB prior to construction. This process involves submitting the building plan to ULB along with other documents. The ULB verifies the plan with other documents and approves the construction. The document which authorizes the construction is called Permit Order. One must have this permit order with him till the completion of construction. ULB officials will inspect various stages of construction and make sure it is compliant with the plan. Once the construction is complete, the Inspection Secretary inspects the building and releases a Completion certificate and finally an Occupancy Certificate. This completes the Building Plan Approval process.

Key Features

The module supports the following key functions -

1. eDCR scrutiny

2. Online submission of application for building permits and occupancy certificates

3. Document Scrutiny

4. Field inspection report capture

5. Pay fee, generate permit order and occupancy certificate online

6. Inspection of applications and online status

7. Configurable workflows

8. Auto fee calculation

9. Send applications back to citizens or reject applications

10. Integration with NOC department

User Roles

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.

Getting Started with BPA

This section of the user manual guides you through the user login process. Citizens can sign up to use the module through the online web portal or the mobile application login interface.

Refer to the Logging Into DIGIT page to learn more about DIGIT user registration, logging in, editing user profile, and logging out.

Using BPA

This section guides you through the details of using the BPA module for each role. Click on the relevant role below to learn more about how to use the module.

Objective

Welcome to the OBPAS product demo script. The key objective of the demo script is to walk users through the OBPAS module and highlight module capabilities and functions.

Module Overview

The Online Building Permission and Approval System or the OBPAS module offers a comprehensive platform that automates the entire building plan approval process. The OBPAS module along with the eDCR scrutiny application streamlines the entire process right from the point of uploading plans for approval to fetching no-objection certificates from concerned authorities and final issue of approvals or permits.

Key Challenges Addressed

The module aims to address key challenges that include -

• Any construction in the city requires prior approval from the local body authorities. Architects and building owners submit a plan diagram that is validated as per the state/city bylaws.

• Most of the building plan applications and drawing plans are submitted manually in paper format since there is a high cost involved for the AUTOCAD license and the absence of cost-effective plan scrutiny solutions.

• The major drawback of the manual permit application process is that it takes more than 45 days to get one permit.

• Iterative plan corrections complicate the process.

• Lack of transparency is another major setback for all stakeholders.

User Benefits

Key benefits of using the OBPAS application -

• Scrutiny is real-time which reduces the time taken for diagram scrutiny. The module routes the uploaded plans through defined workflows for required inspections and approvals.

• It provides access to all authorized stakeholders including department staff, Architects/Consultants, Building owners and Senior Management team based on their role entitlement.

• Being an online system, DIGIT BPA is available anywhere, any place and on any device to the various stakeholders mentioned above. The intuitiveness of the DIGIT-BPA system becomes apparent when even a layman is able to track the status of their submission easily.

Consolidated OBPAS application help ULBs -

• Plan city infrastructure (roads, culverts, drains, streetlights, garbage bins) details better resulting in effective decisions depending upon the type of buildings and their occupancies

• Since capital infra is the second highest expenditure category for any ULB, it is important to know where to invest the funds and resources

• Ensure buildings are not constructed in restricted areas zones (AAI / Water bodies /Monuments)

• Generate revenue and facilitate prompt services to the citizen

Functional Demo

eDCR Scrutiny & Application Submit

The eDCR Scrutiny application digitises the building plan approval. The application features a rules engine required to evaluate the drawing against the existing building by-laws, the scrutiny of the application, configure the internal workflow - inspection, NOCs and finally issuance of approval.

• A stakeholder can be an Architect/Licensed business engineer/town planner who is registered within the ULB. Only a registered stakeholder (architect) can create an application on behalf of the citizen.

• eDCR (development control rules) - which is a rules engine that basically validates the uploaded diagram with that of the by-laws of the state and provides an O/P.

  • UNique reference eDCR number is generated only if it is successful.

  • In case of a failure - the errors are marked in the diagram which can be corrected by the architect and submitted again. This can be iteratively done till scrutiny is successfully completed.

• Using the successfully scrutinized plan diagram parameters, an application is created. Any value which is populated from the plan diagram cannot be modified. There is no manual intervention allowed.

• Discuss the EODB guideline which discusses getting all the application info from citizens in one shot.

  • Here showcase one application from OBPS is getting forked into 3 applications (one for the department to process the permit, one for airport NOC and one for FIRE NOC)

  • Discuss application is smart enough to figure out the list of NOCs required based on the location info gathered from the diagram.

  • The Architect on the creation of an application forwards it to get it concurred from the citizen. If there are any changes, the citizen requests an architect to make those changes or else can inform the architect to submit the application.

  • After getting approval from the citizen, the architect submits the application. On submit, the application fee is auto-generated based on configured payment details. Once the payment is made, the application is forwarded to the department.

    • Application fee can be either paid by the citizen or architect or the citizen can walk into any ULB designated collection counter and make the payment.

Application Processing by Employees

• Submitted applications are available in the ULB clerk inbox for the required processing. Actions by the ULB clerk or counter employee include -

  • Scrutinize the application and documents submitted and check for correctness.

  • Request for additional documents from the applicant

  • Or Upload documents on behalf of the applicant

  • Or Reject the application citing the reason for a rejection

  • Or if the application and documents are in order, the clerk forwards the application for field inspection.

• The Town planning overseer/Engineer does the field inspection of an application. Actions by the Field inspector include -

  • Schedule a meeting with the applicant offline after receiving the request and visit the actual location on the day of field inspection

  • The entire application is designed in a mobile-first approach which will enable the field inspector to use the application on the ground on a mobile phone

  • The field inspection report is designed as a series of checklists with yes and no options to make the process easier for a field inspector.

  • Also, the FI can take photographs of the site and tag them to the application.

    • If no violations are found - FI forwards the application for NOC verification

    • If due to some practical reasons, field inspection is not completed in a single visit - FI does multiple field inspections; the application supports the entry of multiple field inspection details.

    • If some violations are identified, the FI rejects the application.

• NOC Verification - NOC verification responsibility lies with the superintendent of the department.

  • Refer back to the Forking of applications during the application created by Architect

  • Now showcase the status of all 3 applications at the NOC level where you can see the NOC applications are of status in progress.

  • Now login as a FIRENOC department user - process the NOC application and approve it.

  • Now login as Superintendent - showcase the status change from in progress to approved and discuss 3 use cases of NOC integration.

    • One API integration

    • Allowing NOC department users to log in to DIGIT and process the application

    • Completely manual where either the NOC is provided by citizens during application creation or by the Department employee by discussing with the NOC department user.

  • Now approve the NOC step of the application and recommend for approval.

• Executive Engineer/Superintendent engineer can approve the application by entering the permit conditions.

  • There is a calculation logic that runs in the background to calculate the Permit fee using the built-up area and floor area.

  • Also, discuss the importance of permit conditions.

  • Now approve the file.

• The next step is for the Architect or the Citizen to make payment for the permit fee and generate the permit order online.

  • Discuss the info in the permit order

  • QR code info

  • Payment info

  • Approver info

Demo Use Case Scenarios

Possible use case scenarios for the demo -

1. Architect to do eDCR scrutiny

2. Architect to apply for permit application

3. Architect to apply for OC application

4. Citizen to approve/validate the application created by architect

5. Architect and citizen can make payment for application

6. The employee does document scrutiny - can add additional documents if needed

7. The employee does field inspection - update field inspection report- attach photographs of the site if needed

8. The employee does NOC verification - update NOC documents on behalf of NOC department user or citizen if needed.

9. NOC department user to update the NOC details

10. The employee can update the permit conditions

11. Citizens and architects can download the permit order/Occupancy certificate/comparison report, revocation permit PDF and other payment artefacts.

12. The Architect can generate permit orders on create of applications for low-risk applications.

Section 1: Executive Summary

Overview of the Product

The computerised and automatic building permission system offered under the National Urban Stack(NUS) facilitates citizens who seek permission for construction of a building within any Urban Local Body with a transparent, speedy, hassle-free and user-friendly procedure. Online Building Permission System (OBPS) is one of the components of a smart city that has the capability of providing a single window for acquiring building permits, NOCs, and clearances from multiple agencies or departments. Keeping in mind the benefits associated with the product offered, the proposed system is about to be implemented in 500+ ULBs across the country in 15 states and Union Territories. (For details on product features refer to Section-2).

Implementation Methodology for OBPS

For the offered product, the implementation process can be divided into six major distinctive stages. Each stage has predefined entry and exit criteria, roles & responsibilities to assure objective monitoring and decision making for the overall success of the engagement. The whole implementation lifecycle is typical of 35-40 weeks keeping in mind the entry, and exit criteria defined at the beginning and end of each stage is met within the recommended time.

Stage Zero-program setup and onboarding is a pre-requisite for the initiative to kick-off and requires setup of the governance model, implementation Team and decision regarding other significant elements of the initiative like funding and procurement process.

Stage One of the initiative requires scoping of the initiative and deciding on the priorities for implementation by the state implementation Team.

In stage three, the state Team will work upon identifying and finding solutions to the significant gaps in the product offered w.r.t. to the needs of the state.

Configuration and customisation of the product offered in the primary objective of stage four. This involves working on various aspects of state-specific needs and incorporating them into the product suite offered.

In stage four and five, post doing UAT and including all the necessary feedback on the product, the roll-out of the product is done at the state level (Go Live) from a couple of ULBs to pan state coverage. (For details on the implementation plan refer to Section-3).

Manpower Requirement For Implementation

The whole implementation cycle requires a Team of individuals with specific skill sets to work very closely. The state implementation unit comprises individuals with Program management, business analysis, implementation engineering, software engineering, architecture (DCR Domain) and capacity building skills. Depending upon the phases of implementing the initiative is in, the amount of effort by each participant in the smaller units will vary. (For details on resource sizing and requirements refer to Section-5)

Budgetary Requirement For Implementation

Based on close deliberations with various stakeholders, it is recommended that the budgetary allocation for the implementation of the initiative should be around 3 crores to 3.8 crores1 for statewide implementation and Operation and Maintenance Cost (per Year )for the initiative will be approximately 1.35 crores to 2.0 crores2. The budget allocated needs to be utilised for human resources requirements primarily. The budgetary allocation is recommended as per the NICSI standards published on https://www.nicsi.com/ (Check Annexure 1 for NICSI standard rates). The estimation of the budget will increase or decrease based on the rates applicable to the resources required. (For details on budgetary allocation guidelines refer to Section 5).

Critical Success Factors For Implementation

1 Assuming NICSI standard rate cards and 20% range on the actual estimated cost

2 Assuming NICSI standard rate cards and 20% range on the actual estimated cost.

Section 2: Online Building Permission System(OBPS) Implementation Methodology

This section provides an overview of the methodology for the state-wide implementation of OBPS. Implementation of OBPS is distributed across six distinct stages. Each stage has predefined entry and exit criteria, roles & responsibilities to assure objective monitoring and decision making for the overall success of the engagement. Details of each stage are defined in this section.

OBPS implementation program is expected to be completed within approximately 37 weeks with the resource deployment by the State and System Integrator(SI) Team (as defined below). However, it is critical that activities and exit criteria set for each stage are achieved to adhere to this timeline.

Six Stages of Implementation

Stage 0 - Program Setup/Onboarding

Set of initial critical activities that are undertaken on receiving a Letter of Enrollment from the state. Successful completion of these activities assures that the program is started with crucial personnel, System Integrator(SI) Teams and funds.

Stage 1 - Program Kick-Off

This stage envisages the in-person interaction of crucial State officials and implementation System Integrator(SI) Teams to kick-start the program. This stage may require multiple interactions/meetings with different interest groups. The principal objective of these interactions is to identify Pilot ULBs, create an active collaboration & Governance approach and agree on a high-level timeline for the engagement.

Stage 2 - Solution Design

During the Solution design stage key state officials and members, who are subject matter experts, are expected to share state by-laws and also help interpret these laws for the System Integrator(SI) Team. This stage baselines the State-specific product features in the Product Configuration report.

Stage 3 - Configuration & Customization

Configuration & customisation stage, spread across 12 weeks, envisages configuration of the product as per the baselined Product Configuration report and identified state-specific customisations. Active involvement of domain experts from the state Team is required in this stage to validate the implementation of state by-laws.

Stage 4 - UAT & Go Live

During this stage, the active involvement of Pilot ULB officials is expected for thorough testing of the configured product. Training of the key ULB officials will also be undertaken during this stage, along with the promotion of the solution. The establishment of the State support Team and required processes are initiated in this stage.

Stage 5 – Rollout

On successful rollout in the Pilot ULBs, the solution will be rolled out to the rest of the ULBs in batches. Guidance and support from the State Team will be required to create the rollout plans and assure the necessary infrastructure for training and deployment is available at each ULB.

Section 3: Roles and Responsibilities – OBPS Cell, NUS Team & System Integrator(SI)Team

This section outlines the activities involved in each stage of the implementation along with the responsibility and accountability of critical stakeholders - State, NUS Team and Implementation Team onboard.

OBPS Cell: OBPS Cell is the government-appointed body chaired by the Principal Secretary/Secretary, Urban Development Department with members from the Town and Country Planning Organization, Urban Development Department etc.

NUS Team: NUS Team is the National Program Management Unit established in Delhi which will provide all necessary support to the state concerning the implementation, Program Designing etc.

System Integrator (SI)Team: SI Team will be responsible for the rollout of the initiative in the state, providing all end to end support to the state w.r.t. The implementation of the products in the ULBs.

Execute - One who owns the accountability to complete the activity

Consult - One who may initiate, guide and in the process, handhold the execution of the activity

Section 4- Resource, effort estimation and Budget Requirements for the Program

Implementation effort and Budget requirements of the program(Stage 1 to Stage 5)

Implementation Budget requirements of the program

The summary of the budgeting is as per the NICSI rates(Please refer to annexure-1) and assuming a 20% range.

Resource requirements for the OBPS cell required to be formed by the state

Project Sponsor: Is the Head of the OBPS Cell who will drive the project from the State Side

Plan Process Expert: The two resources that will provide the BPA application process and workflow. Validate the UAT in compliance with the expected outcome.

Development Control Rules Experts: they should have the domain skills on the drawings and plan along with the DCR rules of the State. They would provide the templatization of the DCR Rules, validate the same once configured in the Application and approve.

Nodal Officer: He would play the organise role who will provide all logistics support and scheduling of activities related to the project, Rollout and training of both Engineers and ULB officials across the State.

Introduction

The Building Usage data allows States/ULBs to classify the buildings based on occupancy types, sub-types and its actual usage. Permits and approval process are dependent on the Usage type. The Data Table provides the details required to configure the Building Usage types. Refer to the National Bye-Laws to view the prescribed list of usage types.

Data Table

Data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify all the building usage and its mapping with sub occupancy and then fill into the template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Introduction

Building Occupancy classifications help in categorizing structures based on the proposed use of the building. Occupancy categories determine the required permits and approvals. The Building Occupancy types data is hence a vital parameter used to define approval workflows in the OBPS module. Refer to the National Bye-Laws to view the prescribed list of occupancy types.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify the occupancy which is applicable. Refer to National Bye-Laws to learn more about occupancy types and names.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Introduction

Stakeholders refer to the technical persons and end-users of the OBPS system. The Stakeholders Type masters list allows the registration of stakeholders in the OBPS system. The list of stakeholders varies from one State/ULB to another.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify the stakeholders and fill into the given template. Refer to the National Bye-Laws for more details on stakeholder types and defined limitations.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Introduction

The Inspection checklist contains the list of activities that a field inspector should consider and check while on the field. The checklist is configurable at the State/ULB level.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definitions

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify all the checkpoints service wise and then fill into the given template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Introduction

Building Sub Occupancy details refer to sub-categorization of primary occupancy types. For instance, residential buildings can be further classified as apartments or old age homes depending on the specific usage of the buildings. Refer to the National Bye-Laws to view the prescribed list of sub-occupancy types.

Data Table

The data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify the sub occupancy which is applicable. Refer to National Bye-Laws to learn more about occupancy types and names.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachment

Introduction

Town Planning Schemes masters list contains all building plan approval schemes and sub-schemes available for the benefits of the citizens. Create a list of the available schemes and map these schemes to specific Occupancy Types.

Data Table

Data given in the table is sample data for reference.

Procedure

Data Definition

Steps to fill data

1. Download the data template attached to this page.

2. Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.

3. Reach out to the person who shared the template for further details or to clear your doubts. Identify if the State/ULB has a provision for capturing pipe size for connections.

4. Identify all the scheme and sub-schemes and fill into the given template.

5. Go through the checklist to verify the data. Make sure that each and every point mentioned in the checklist is covered.

Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data entry requirements are met. These activities have been divided into 2 groups as given below.

Common Checklist

This checklist covers all the activities which are common across the entities.

Entity Specific Checklist

There is no separate entity-specific checklist for this entity.

Attachments

Document Verifier (DV)

The Document Verifier (DV) is responsible for verifying the required and supporting documents uploaded by the citizen or the stakeholder with the building permit or occupancy certificate application. The application is forwarded to the Field Inspector for further review once the DV finds the documents uploaded meet the requirements. Else, the application is either sent back to the citizen for refurbishing the documents or rejected.

DV can

Send applications back to citizens

DV can send the application back to the citizen for any corrections or if any vital document has not been uploaded. The DV can also upload the documents on behalf of the citizens.

To send the application back to the citizen

Click on the OBPS Inbox option on the home screen.

Click on the Application No. hyperlink available in the list of applications Inbox of the employee dashboard.

Or, enter Application No. or any other search parameter to search for the application.

Click on the Application No. link to open the application.

Scroll down the application page to review the filled-in details.

Review the documents uploaded by the citizen.

Click on the Take Action button at the bottom of the application page once the review is complete.

Click on the Send Back to Citizen button if the documents do not meet the application requirements or any document is missing.

Select the applicable Assignee Name. State the reasons for sending the application back to the citizen in the Comments section.

Click on the Choose File button to upload any supporting documents. Click on the Send Back to Citizen button.

The application is placed back in the Citizen queue for required edits.

Reject Application or Revoke Application

The DV can reject the application if the documents and information furnished by the citizen do not meet the permit or occupancy guidelines.

To reject application

Enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application.

Scroll down the application page to review the filled-in details.

Click on the Take Action button at the bottom of the application page once the review is complete.

Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.

State the reasons for rejecting the application in the Comments section. Click on the Upload Files button to upload any supporting documents. Click on the Reject button.

The application is rejected and a notification is sent to the owner informing the same.

Permit orders are sanctioned instantly for low-risk applications. However, the application goes through the normal workflows for document verification, field inspection, and NOC verification. The ULB authorities can revoke the permit order in case any anomalies are detected during the verification process.

Applications can be revoked at any stage by the Document Verifier, Field Inspector, or NOC Verifier.

To revoke application

Click on Application No. in the employee Inbox or enter Application No. or any other search parameter to search for the application.

Click on the Application No. link to open the application. Scroll down the application page to review the filled-in details.

Click on the Take Action button at the bottom of the application page once the review is completed.

Click on the Revocate button if the application details do not meet the permit requirements.

Enter the reason for revoking the permit in the Comments field.

Click on Choose File to attach supporting documents. Click on the Revocate button. The permit order is revocated.

Verify and forward application

The DV verifies and forwards the application if the documents and information provided in the application are found satisfactory and complete.

To verify and forward the application

Enter the Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application.

Scroll down the application page to review the filled-in details. Click on the Take Action button at the bottom of the application page once the review is complete.

Click on the Forward button once all documents are verified.

Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section.

Click on the Choose File button to upload any supporting documents. Click on the Forward button.

The application is forwarded to the field inspector for further processing.

Field Inspector (FI)

The field inspector or FI is responsible for conducting the field inspection of the construction site and premises. The FI prepares the inspection report based on the observations on the defined inspection parameters.

The FI can

Prepare Inspection Report

FI prepares the field inspection report and attaches the report to the application.

To prepare the inspection report

Click on the Application No. hyperlink available in the list of applications available in the employee Inbox.

Or, enter Application No. or any other search parameter to search for the application. Click on the Application No. link to open the application.

Scroll down the application page to review the filled-in details. Enter the Inspection Date and Inspection Time in the panel. FI can add multiple field inspection reports as required.

Mark Yes or No as applicable for each item in the Inspection Checklist. Enter any additional information in the Remarks section available for each item in the checklist.

Select the applicable Document Type for each of the listed Documents. Click on the Upload File button to upload the relevant documents.

Click on +Add Another Field Inspection Report button to append additional inspection details.

Click on the Take Action button at the bottom of the application page once the review is complete.

Send applications back to citizens

To send the application back to the citizen

Click on Send Back to Citizen if any information or document is missing from the application.

Select the applicable Assignee Name. State the reasons for sending the application back to the citizen in the Comments section.

Click on the Choose File button to upload any supporting documents. Click on the Send Back to Citizen button.

The application is placed back in the Citizen queue for required edits.

Reject application

The FI can reject the application if the documents and information furnished by the citizen do not meet the permit or occupancy guidelines.

To reject the application

Click on the Reject button if the documents do not meet the application requirements or the information provided in the application is inaccurate.

State the reasons for rejecting the application in the Comments section. Click on the Choose File button to upload any supporting documents. Click on the Reject button.

The application is rejected and a notification is sent to the owner informing the same.

Revocate application

The FI can revocate an application if the documents and information furnished by the citizen do not meet the guidelines.

To revocate the application

Click on the Take Action button.

Enter the reason for revoking the application in the Comments field. Click on Choose File to attach supporting documents. Click on the Revocate button.

Forward application

The FI verifies and forwards the application if the documents and information provided in the application are found satisfactory and complete.

To forward the applications

Click on the Verify and Forward button.

Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section.

Click on the Choose File button to upload any supporting documents. Click on the Verify and Forward button.

The application is forwarded to the NOC Verifier for further processing.

NOC Verifier

The NOC Verifier is responsible for checking the no-objection permissions obtained for various civic authorities in the context of the building construction. Commonly, a NOC is required from the Airports Authority and the Fire department to certify all guidelines are met by the builder and owner. If all requirements are met the NOC verifier forwards the application to the BPA Approver.

NOC Verifier can

• Send applications back to citizens

Send applications back to citizens

The NOC Verifier can send the application back to the citizen in case there are some details missing in the form.

To send the application back to the citizen

Click on the OBPS Inbox option on the home screen.

Click on the Application No. hyperlink available in the list of applications in the employee Inbox. Or, enter Application No. or any other search parameter to search for the application.

Click on the Application No. link to open the application.

Scroll down the application page to review the filled-in details.

Review the inspection report and NOC documents uploaded with the application. Click on the Choose File button to upload NOC documents on behalf of the NOC issuing authority like Fire or Airport.

Click on the Take Action button at the bottom of the application page once the review is complete.

Click on the Send Back to Citizen button if the documents do not meet the application requirements or if any document is missing.

Select the applicable Assignee Name. State the reasons for sending the application back to the citizen in the Comments section.

Click on the Choose File button to upload any supporting documents. Click on the Send Back to Citizen button.

The application is placed back in the Citizen queue for required edits.

Reject application

The NOC Verifier can reject the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.

To reject the application

State the reasons for rejecting the application in the Comments section. Click on the Choose File button to upload any supporting documents. Click on the Reject button.

The application is rejected and a notification is sent to the owner informing the same.

Revocate application

The NOC Verifier can revocate the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.

To revocate the application

Click on the Application No. link to open the application. Scroll down the application page to review the filled in details.

Click on the Take Action button at the bottom of the application page once the review is completed.

Click on the Revocate button if the application details do not meet the permit requirements.

Enter the reason for revoking the permit in the Comments field.

Click on Choose File to attach supporting documents. Click on the Revocate button.

Forward application

The NOC Verifier verifies and forwards the application to the BPA Approver if the documents and information provided in the application are found satisfactory and complete.

To forward the applications

Click on the Verify and Forward button once all details are verified and found satisfactory.

Select the applicable Assignee Name who will carry out the next phase of verification. Provide any additional information for the assignee in the Comments section. Click on the Choose File button to upload any supporting documents. Click on the Verify and Forward button.

The application is forwarded to the BPA Approval for final approval.

BPA Approver

The BPA Approver is responsible for approving or rejecting the application for building permits or occupancy certificates. Once approved the owner can download the permit or the occupancy certificate from the portal.

The BPA Approver can

Approve application

The BPA Approver approves the application for a building permit or occupancy certificate once the verification is complete and prescribed guidelines are met.

To approve applications

Click on the OBPS Inbox option on the home screen.

Click on the Application No. hyperlink available in the list of applications section of the employee dashboard.

Or, enter Application No. or any other search parameter to search for the application.

Click on the Application No. link to open the application.

Scroll down the application to review the filled-in details.

Review the documents uploaded with the application

Check the applicable conditions in the Permit Conditions list.

Click on the Take Action button at the bottom of the application page once the review is complete.

Provide any additional information for the assignee in the Comments section.

Click on the Choose File button to upload any supporting documents.

Click on the Approve button once all requirements are complete.

The application is approved. The citizen or the stakeholder can now download and print the building permit or occupancy certificate from their account only after paying the permit fee. There is no fee applicable for an occupancy certificate.

Reject application

BPA Approver can reject the application if the documents and information furnished by the citizen do not meet the prescribed guidelines.

To reject applications

State the reasons for rejecting the application in the Comments section. Click on the Choose File button to upload any supporting documents. Click on the Reject button.