Development Control Rules (Digit-DCR)

Introduction

Currently, ULBs follow a complete manual mass mode of providing various building-related approvals and related NOCs. This delays the approval process and creates a lot of inconvenience for applicants and architects. There is also a lack of transparency and accountability in this manual approach. Due to the complexity of scrutiny and approval processes and the involvement of various stakeholders, there are several challenges in the system. Some of the issues are-Complex rules and bye-laws and their interpretation, the time-consuming process of issuance of Planning Permission, increased chances of human errors due to manual submission and scrutiny, inadequate citizen interface and no single point of contact, etc.

The manual scrutiny of the building bye-laws is replaced with “Digit-DCR”.Digit-DCR is capable of reading the drawing, extracting parameter values, applying them to bylaws and generating the acceptance or rejection information in seconds. This process provides a leap of 15 days of cumbersome manual work to a few seconds. The Digit-DCR is even capable of marking mistakes and failing details. It converts details of drawing like Site plans, Floor plans, Elevation, etc to pdf and saves them in the system.

Prerequisites

Knowledge on following

Java
Basics of 2D Drawing like ( Top view, Front view, Side view, etc)
Basic Math

Functionality

High-level design

Sequence Diagram

Configuration and Set up

References and Notes

Layer Name Standards

The general Practice of the Architects is to draw diagrams in the default layer with the name “0” with portions stating Section Plan, Floor Plan, etc. With this approach, it is not possible to extract parts of the building for Bye-Laws validation. Hence Parts of the buildings should be drawn in specific layers. These layers also should have a standard format for machine reading.

For example, Plan will have a “Bathroom” and "Washbasin” which should be validated for dimensions and counts for Sanitation. Hence these sanitation-related parts should be drawn in a layer called “BLK_1_WATER_CLOSET” layer, where “BLK_1” states it is block 1 and “WATER_CLOSET” states it is a toilet. Another example is Toilets for the disabled should be validated floor wise Hence it should be defined as Floorwise layer names like “BLK_1_FLR_0_SP_WC” layer.

We cannot define a complete set of layer names with these combinations because it is based on the following parameters

Number of Blocks
Number of Floors in each Block
Number of Polygons on each floor
Number of levels

So when data is required at Plan Level, Block Level, Floor Level, or Height it is named and prefixed accordingly

Plan Level

At the Plan level, the layer names are used without any prefixes. The list of such layer names are

1	PLOT_BOUNDARY
2	VERT_CLEAR_OHEL
3	HORIZ_CLEAR_OHEL
4	WASTE_DISPOSAL
5	PLAN_INFO

Block Level

Block Level Layer Names
1	BLK_*_COVERED_AREA
2	BLK_*_COVERED_AREA_DEDUCT
3	BLK_*_BATH
4	BLK_*_WC

Floor Level

Floor Level Layer Names

BLK_*_FLR_*_BLT_UP_AREA

BLK_*_FLR_*_BLT_UP_AREA_DEDUCT

Color Code Standards

Some parts of the building and its validation is based on Usage(Occupancy) types. For example, every floor in which all types of usage present have to be defined. Based on usage type parking has to be calculated. So only layer name is not sufficient to differentiate but colour also to include. Hence Floorwise built-up area will be defined in “BLK_1_FLR_0_BLT_UP_AREA” with index colour 2 for Residential type of usage. All colours are defined based on Occupancy type. The below list provides the colour codes for each occupancy-