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 11 Next »

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.

Stakeholder type Name*

Code*

Stakeholders Permit Validity (In Years)

Limitations on construction (Briefly)

1

Builders

BLD

2

N/A

Architect

ARC

2

N/A

Town Planner

TPR

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.

Column Name

Data Type

Data Size

Mandatory

Description

1

Stakeholder type name

Text

64

Yes

Name provided for stakeholder type which is ideally 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

Stakeholders 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 (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

  1. Enter the Stakeholder Type Name.

  2. Enter a unique Code to identify the listed stakeholder.

  3. Enter the value to define the Stakeholders Permit Validity (In Years).

  4. Enter a brief description of Limitations on Construction applicable for the listed stakeholder. Refer to the National Bye-Laws for more details on stakeholder types and defined limitations.

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.

Checklist

Entity Specific Checklist

Separate Entity Specific Checklist is not required for this module data.

Attachments

  1. Stakeholder Type Template

2. Stakeholder Type Sample

  • No labels