...
Note: The records in the above table are sample entries.
Procedure
Data Definition
Field(s) Description :
Sr. No. |
|---|
...
ColumnName | Data Type | Data Size | Mandatory | Description | |
|---|---|---|---|---|---|
1 | Stakeholder type name | Text | 64 | Yes | Name provided for stakeholder type which is ideals the technical qualification of the person registering. |
...
2 | Code | Alphameric | 3 | Yes | Unique Code provided with respect to Stakeholders type. It can be alphabetical, numeric, and alphanumeric as well. |
3 | Permit |
...
valid (In years) | Numeric | 64 | No | All the permits have a validity period within which a site plan is valid. This depends upon the qualifications of the technical person. |
4 | Limitations on |
...
construction (Briefly) | 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.
...
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 expectation. 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. |
Attachments
Stakeholder Type Sample
| View file | ||
|---|---|---|
|
2. Stakeholder Type Template
...