Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Introduction

Stakeholders are the technical person and end-users of the OBPS system. For stakeholders registration OBPS system contains the master list for the same. This master is been described below.

Data Table

Sr. No.

Stakeholder type Name*

Code*

Permit Validity (In Years)

Limitations on construction (Briefly)

1

Builders

BLD

2

N/A

2 

Architect

ARC

2

N/A

3 

Town Planner

TPR

5

Can construct 3 floors building, up to a height of 300 mts.

Note: The records in the above table are sample entries.

Procedure

Data Definition

Field(s) Description :

  1. Sr.No.: Defines the serial no of the line item.

  2. Stakeholders type name: Name provided for stakeholder type which is ideals the technical qualification of the person registering.

  3. Code: Unique Code provided with respect to Stakeholders type. It can be alphabetical, numeric, and alphanumeric as well.

  4. Permit Validity: All the permits have a validity period within which a site plan is valid. This depends upon the qualifications of the technical person.

  5. Limitations on the construction: Building Bye-laws defines and permits the limitations on the type of construction any technical person can take up to. This field captures such information.

Steps to fill data

  1. Identify the “Stakeholders type” that exists at a ULB/ State level.

  2. Priory, there are certain Stakeholders type which is already mentioned in the national bye-law (http://mohua.gov.in/upload/uploadfiles/files/Chap-4.pdf)

  3. Collect the above information and feed it below the “Stakeholders types Name” column accordingly.

  4. Add the “Code” respectively against the identified Usage type Name(s).

  5. The format of the Code will either be predefined or can be a continuous numeric/alphanumeric sequence as per the requirement.

  6. Fill up the permit valid years that exist with ULB/State or as per National Building Bye-law.

  7. Fill up the “Limitation on the construction” briefly as per the available information at ULB/State level.

Validations

  1. All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed.

  2. A “single entry” should be made against the respective column. In the case of multiple entries, continuation must be followed.

  3. The code can be alphanumeric as provided by the state

Attachments

Stakeholder Type Sample

Stakeholder Type Template

  • No labels