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
Sr. No. | Code* | Stakeholder |
---|
...
Type Name* |
---|
...
Code*
Stakeholder Permit Validity (In Years) | Limitations on construction |
---|
...
1 | BLD | Builders |
...
BLD
2 | N/A | |
2 | ARC | Architect |
...
ARC
2 | N/A | |
3 | TPR | Town Planner |
...
5 | Can construct 3 floors building, up to a height of 300 mts. |
Note: The
...
above table
...
contains sample
...
data for reference.
Procedure
Data Definition
...
Sr. No. |
---|
...
Stakeholders type name: Name provided for stakeholder type which is ideals the technical qualification of the person registering.
...
Column Name | Data Type | Data Size | Is Mandatory? | Description | |
---|---|---|---|---|---|
1 | Code | Alphanumeric | 3 | Yes | Unique Code provided with respect to Stakeholders type. It can be alphabetical, numeric, and alphanumeric as well. |
2 | Stakeholder Type Name | Text | 64 | Yes | Name provided for stakeholder type which is ideally the technical qualification of the person registering. |
3 | Stakeholder Permit Validity |
...
(In Years) | Numeric | 64 | No | All the permits (Permits to the stakeholders) have a validity period within which |
...
he/she is authorized. | |
4 | Limitations on |
...
construction | Text | 612 | No | 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
Identify the “Stakeholders type” that exists at a ULB/ State level.
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)
Collect the above information and feed it below the “Stakeholders types Name” column accordingly.
Add the “Code” respectively against the identified Usage type Name(s).
The format of the Code will either be predefined or can be a continuous numeric/alphanumeric sequence as per the requirement.
Fill up the permit valid years that exist with ULB/State or as per National Building Bye-law.
Fill up the “Limitation on the construction” briefly as per the available information at ULB/State level.
Validations
All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed.
A “single entry” should be made against the respective column. In the case of multiple entries, continuation must be followed.
The code can be alphanumeric as provided by the state
Attachments
Stakeholder Type Sample
View file | ||
---|---|---|
|
Stakeholder Type Template
Download 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 the stakeholders and fill into given 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 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.
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
There is no separate entity-specific checklist for this entity.