Introduction
Buildings are classified The Building Usage data allows States/ULBs to classify the buildings based on occupancy types, sub-types subtypes and then its actual usage for obtaining permission. These are used to configure Building usage types in the OBPS module which has been described in the table below.We can also refer to National Building Bye-law for understanding- http://mohua.gov.in/upload/uploadfiles/files/Chap-4.pdf. 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
Sr. No. | Usage Code* | Usage Name* Code (Usage)(In English) | Usage Name* (In Local Language) | Sub Occupancy Code* | Sub occupancy Occupancy Name* | |
|---|---|---|---|---|---|---|
1Apartment type | A-AF-AH | Apartment type | अपार्टमेंट प्रकार | AF | Apartment/Flat | |
2 | Family residential | A-AF-FR | ApartmentFamily residential | परिवार आवासीय | AF | Apartment/Flat |
3 Residential flat | A-AF-RF | Residential flat | आवासीय फ्लैट | AF | Apartment/Flat |
Note: The records in the above table are contains sample entriesdata for reference.
Procedure
Data Definition
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Description | |
|---|---|---|---|---|---|---|
1 | Usage Code | Alphameric | 7 | Yes | Unique Code for listed Usage name. It can be a combination of alphabets and numbers. | |
2 | Usage Name (In English) | Text | 64 | Yes | Type of usage of the building to be mentioned here.2 | |
3 | Code (Usage) | Usage Name (In Local Language) | Text | 64 | Yes | Type of usage of the building to be mentioned here. |
4 | Sub Occupancy Code | Alphameric | 7 | Yes | Unique Code provided with respect to Usage name. It can be numeric and alphanumeric as well. | 3Sub Occupancy code to be mentioned here. Maps the Building Usage details to specific sub occupancy type. |
5 | Sub Occupancy Name | Text | 64 | yesNo | Sub Occupancy Name in the to be mentioned here. Maps the Building Usage details to specific sub occupancy type. |
Steps to fill data
Identify the “Usage Name ” that exists at a ULB/ State level.
Priory, there are certain Usage type which is already mentioned in the national bye-law (http://mohua.gov.in/upload/uploadfiles/files/Chap-4.pdf)
Collect the above information and feed it below the “Usage Name” column accordingly.
Add the “Usage Code” respectively against the identified Usage type Name(s).
The format of the Usage Code will either be predefined or can be a continuous numeric/alphanumeric sequence as per the requirement.
Fill up the sub occupancy name column accordinglyDownload the data template attached to this page.
Refer to the ‘Data Definition’ section of this document to understand the headers in the template sheet, their data type, size, and definitions.
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.
Identify all the building usage and its mapping with sub occupancy and then fill into template.
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 one the data is filled into a template to ensure data type, size, and format of data is as per the expectationentry 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.
Sr. No. | Checklist Parameter | Example |
|---|---|---|
1 | Make sure that each and every point in this reference list has been taken care of. |
Entity Specific Checklist
Not ApplicableThere is no separate entity-specific checklist for this entity.