Introduction
Once the Trade Ontology is defined, the next step is to allocate the license fee associated with the Trades.
Dependent on the Trade Classification Level (Types/ Subtypes), the fee allocated might be same across the Sate or could vary from ULB to ULB. There could be a distinct fee(s) for two different types of applications (new and renewal).
Following are the key tasks to be executed :
Allocate the License Fee according to Trade Classification Level (Types/Subtypes).
Map the License fee with respective Trade Classification Level.
Data Table
Sr. No |
|---|
...
Trade |
|---|
...
Sub Type Code* |
|---|
...
Trade |
|---|
...
Sub Type Name (In English) |
|---|
...
New License Fee* |
|---|
...
Renewal License Fee* | UOM |
|---|
...
UOM From | UOM To | ||||||
|---|---|---|---|---|---|---|---|
1 | TRADE_SMALL_BAKERY | Small Bakery | 2500 | 2000 | Workers | 1 | 20 |
2 | TRADE_SMALL_BAKERY | Small Bakery | 3000 | 2500 | Workers |
...
21 |
...
30 | |||||||
2 | TRADE_MED_BAKERY | Medium Bakery | 5000 | 4500 | Workers | 1 | 30 |
(Note: The Rows in the above table consists of Sample Data)
Procedure
Data Definition(s)
Sr. No |
|---|
...
Trade Subtype Code: Unique Identifier for Trade Sub Type which is used as a reference for child configuration mapping.
...
Trade Subtype Name (Eng): Nomenclature of “Trade Sub Type ” in English.
...
. | Column Name | Data Type | Data Size | Is Mandatory? | Description |
|---|---|---|---|---|---|
1 | Trade Sub Type Code | Reference | 64 | Yes | The Code assigned to the Trade Sub Type. Eg: TRADE_SMALL_BAKERY is assigned to Bakery |
2 | Trade Sub Type Name (In English) | Text | 256 | Yes | Name of the Trade Sub Type in English. Eg: Small Bakery |
3 | New License Fee | Decimal | (6,2) | Yes | The fee charged as when the license applied for the respective trade for the first time. |
4 | Renewal License Fee |
...
Decimal | (6,2) | Yes | The fee charged as |
...
when the license applied for the respective trade for the renewal. |
...
5 | UOM | Text | 64 | No | The Units of Measurement” associated with the Trade. Eg : Workers is the UOM associated with the trade “Bakery” |
6 | UOM From |
...
Integer | 6 | No | Initial Range from which the “Units of Measurement” is applicable for a Trade |
...
7 | UOM To |
...
Integer | 6 | No | Final Range to which the “Units of Measurement” is applicable to a Trade |
...
...
How to fill data
Download the data template attached to this page.
...
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
Identify the “Trade Sub Types” that exists at a ULB/ State level.
Collect the above information and feed it below the “Trade Sub Type Name” column accordingly.
...
The Description of Trade Sub Type Name must be provided as per the language specified in the respective column.
Add the “Trade Sub Type Code” respectively against the identified trade type(s)
...
.
Fill in the New License Fee & New Renewal Fee accordingly.
...
The New License Fee & Renewal Fee can be the same as well as distinct, depending on the by-laws/ mandate followed by the State/ULB.
Fill in the fields related to Units of Measurement (UOM Unit, From/To) for the available trades only.
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. Incase of multiple entries, continuation must be followed.
The “Trade Sub Type Name” must be provided in the required language as mentioned against the respective column.
The format of Trade Sub Type Code must be informed to the individual/team responsible for filling in the master data.
The Trade Rates must be defined as a “Whole Number” and must not be :
In Range.
In Fractions/ Decimals.
Attachments
...
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. |
Entity Specific Checklist
This checklist covers the activities which are specific to the entity.
Sr. No. | Checklist Parameter | Example |
|---|---|---|
1 | Trade Type Name (In either Language) should not contain any special characters. | Small Bakery: [Allowed] #Small_Bakery! : [Not allowed] |
Attachments
...
...
...
...