1 of 57

Configuration

Master Data Templates

Configure master data templates for MUKTASoft

Objective

This section is designed with the objective of helping implementation parties and end-users collect the required master data through minimal interaction and iterations and ensure the quality, consistency and shape of data needed to configure the system.

Audience

This page is intended to help stakeholders as given below on data gathering activities.

State Team
eGov Onsite Team/ Implementation Team
ULB Team (Nodal and DEO)
Implementation Partners

Output Artefacts

The artefacts of this document are the data template of a configurable entity, a page with content defining the entity template and helping on how to fill the template with required data.

Data Entry

Download the data template attached to this page.
Find the meaning of the different headers in the Data Definition section on this page
Make sure all the headers, data type, field size and definition/ description are clear. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify the different types of user roles on the basis of ULB functions.
Start filling the data starting from serial no. and complete a record at once. Repeat this exercise until the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

Checklist

The checklist is a set of activities to be performed once 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

Make sure that each and every point in this reference list has been taken care of

Entity Specific Checklist

This checklist covers the activities specific to the entity.

Sr. No.

Activity

Example

The Code should be alphanumeric and unique

The Name should not contain any special characters

Project Type

Introduction

Project types are the category of works which are included and executed under the scheme MUKTA.

Data Table

Sr. No.

Code*

Project Type*

Project Type (Odiya)

Effective From

Effective To

Is Active

Drainage and sewerage work [Except de-siltation]

01/04/2022

Yes

Sanitation work [Except road sweeping and drain cleaning]

Water conservation and rain water harvesting structures

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Local Language)

Text

256

Project type name in local language

Effective From

Date

Yes

Date from which the project is effective

Effective To

Date

Date till which the project is effective

Is Active

Boolean

Yes

Whether the project is active or not

Attachments

Target Demography

Introduction

Target demography are the areas which are on prime focus of Government for the employment and improvement.

Data Table

Sr. No.

Code

Project Type

Project Type (Odiya)

Effective From

Effective To

Is Active

Slum

ବସ୍ତି

Area inhabited by SC

ଅନୁସୂଚିତ ଜାତି (ଏସ.ସି)ସମ୍ପ୍ରଦାୟ ବାସ କରୁଥିବା ଅଞ୍ଚଳ

Area inhabited by ST

ଅନୁସୂଚିତ ଜନଜାତି (ଏସ.ଟି)ସମ୍ପ୍ରଦାୟ ବାସ କରୁଥିବା ଅଞ୍ଚଳ

Area inhabited by Minorities

ସଂଖ୍ୟାଲଘୁ ସମ୍ପ୍ରଦାୟ ବାସ କରୁଥିବା ଅଞ୍ଚଳ

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date

Date from which the project is effective

Effective To

Date

Date till which the project is effective

Is Active

Boolean

Whether the project is active or not

Attachments

Unit Of Measurement (Units)

Introduction

Unit of measurements is the units used to capture the measurement and create the estimate for work in MUKTA.

Data Table

Sr. No.

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

CUM

Cubic Meter

ଘନ ମିଟର

SQM

Square Meter

ବର୍ଗ ମିଟର

RMT

Running Meter

ରନିଙ୍ଗ ମିଟର

Kilogram

କିଲୋଗ୍ରାମ

NOS

Numbers

ସଂଖ୍ୟାଗୁଡିକ

CFT

Cubic Feet

ଘନ ଫୁଟ

SFT

Square Feet

ବର୍ଗ ଫୁଟ

Feet

ଫୁଟ

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Description

Text

256

Yes

Provides the name of the project type

Description (Odiya)

Text

256

Project type name in local language

Effective From

Date

Date from which the project is effective

Effective To

Date

Date till which the project is effective

Is Active

Boolean

Whether the project is active or not

Attachments

Overheads

Introduction

Overheads are the items other than SOR and Non-SOR which are included in the estimate to complete the estimation and arrive at the final value of work.

Data Table

Sr. No.

Code

Description

Description (Odiya)

Is work order value?

Calculation Method

Percentage/ Value

Effective From

Effective To

Is Active

Supervision Charge

ତଦାରଖ ଦେୟ

Yes

Percentage

7.5

GST

Goods and Service Tax

ଦ୍ରବ୍ୟ ଏବଂ ସେବା କର

Yes

Percentage

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Description

Text

256

Yes

Provides the name of the project type

Description (Odiya)

Text

256

Project type name in local language

Is work order value?

Boolean

Calculation Method

Identifier

Percentage/Value

Numeric

Effective From

Date

Date from which the project is effective

Effective To

Date

Date till which the project is effective

Is Active

Boolean

Whether the project is active or not

Attachments

Skill Category & Skills

Introduction

Skills are defined for the wage seekers and have different wages defined for each skill category. These wages are revised by the government over a period of time.

Data Table

Sr. No.

Data Definition

Attachments

Community-Based Organisation Roles

Role definition master data templates

Introduction

In MUKA community-based organizations have different roles to play based on the work value. The role defined is Implementation Agengency and Implementation Partner.

Data Table

Sr. No.

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

Scheme

Introduction

MUKTA is known as a scheme and it is configured in the system along with its HOAs.

Data Table

Sr. No.

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

Expense Heads

Introduction

These are the heads under which MUKTA expenditure is booked.

Data Table

Sr. No.

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

Standard Deductions

Introduction

These are deductions which are made from the purchase bills and then remitted to respective departments.

Data Table

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

Organisation Type

Introduction

The Community Based Organization and Vendors are created as 2 different type of organization.

Data Table

Sr. No.

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

Organisation Sub Type

Introduction

The Community Based Organization are further categories and refered as sub type.

Data Table

Sr. No.

Parent Code (Org Type)

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

Organisation Functional Category

Introduction

The organization's functional category define the functional area of an organization.

Data Table

Sr. No.

Parent Code (Org Type)

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

Organisation Class/Rank

Introduction

The rank/ class of the organization defined helps the government to choose the right organization for work.

Data Table

Sr. No.

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Attachments

HRMS Designation

Introduction

These are designations of the employees working within the ULB across different sections.

Data Table

Sr. No.

Parent Code

Code

Description

Description (Odiya)

Effective From

Effective To

Is Active

WRK

Executive Engineer

କାର୍ଯ୍ୟନିର୍ବାହୀ ଯନ୍ତ୍ରୀ

WRK

DEE

Deputy Executive Engineer

ଡେପୁଟି କାର୍ଯ୍ୟନିର୍ବାହୀ ଯନ୍ତ୍ରୀ

WRK

AEE

Assistant Executive Engineer

ସହକାରୀ କାର୍ଯ୍ୟନିର୍ବାହୀ ଯନ୍ତ୍ରୀ

WRK

Municipal Engineer

ମ୍ୟୁନିସିପାଲିଟି ଇଞ୍ଜିନିୟର୍ (ଯନ୍ତ୍ରୀ)

WRK

City Enginner

ସିଟି ଇଞ୍ଜିନିୟର୍ (ଯନ୍ତ୍ରୀ)

WRK

Assistant Enginner

ସହକାରୀ ଯନ୍ତ୍ରୀ

WRK

Junior Enginner

କନିଷ୍ଠ ଯନ୍ତ୍ରୀ

WRK

Revenue Inspector

ରାଜସ୍ୱ ନିରୀକ୍ଷକ

WRK

Ameen

ଅମିନ୍

WRK

Dealing Assistant

ସଂପୃକ୍ତ ସହାୟକ

WRK

Program Coordinator (MUKTA)

ପ୍ରୋଗ୍ରାମ(କାର୍ଯ୍ୟ) ସଂଯୋଜକ (ମୁକ୍ତା)

WRK

Implementation Expert (MUKTA)

କାର୍ଯ୍ୟାନ୍ୱୟନ /କାର୍ଯ୍ୟକାରୀ ବିଶେଷଜ୍ଞ (ମୁକ୍ତା)

WRK

ACCE

Account Expert (MUKTA)

ଆକାଉଣ୍ଟ ବିଶେଷଜ୍ଞ (ମୁକ୍ତା)

ACC

Accounts Officer

ଆକାଉଣ୍ଟସ୍ ଅଫିସର(ହିସାବ ଅଧିକାରୀ)

ACC

JAO

Junior Accounts Officer

କନିଷ୍ଠ ଆକାଉଣ୍ଟସ୍ ଅଫିସର(ହିସାବ ଅଧିକାରୀ)

ADM

Commissioner

କମିଶନର

ADM

ADMC

Additional Commissioner

ଅତିରିକ୍ତ କମିଶନର

ADM

DMC

Deputy Commissioner

ଡେପୁଟି କମିଶନର

ADM

AMC

Assistant Commissioner

ସହକାରୀ କମିଶନର

ADM

Executive Officer

କାର୍ଯ୍ୟନିର୍ବାହୀ ଅଧିକାରୀ

ADM

AEO

Assistant Executive Officer

ସହକାରୀ କାର୍ଯ୍ୟନିର୍ବାହୀ ଅଧିକାରୀ

Tax

Ward Officer

ୱାର୍ଡ ଅଫିସର

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

User Role

Introduction

The roles defined in the system carry specific functionality and need to map with users when created in the system to enable the user to use the respective functionality.

Data Table

Sr. No.

Code

Role Description

Action

Service

PROJECT_CREATOR

Poject Creator

Create Search View Modify

Project

PROJECT_VIEWER

Project Viewer

Search View

Project

ESTIMATE_CREATOR

Estimate Creator

Inbox Create Search View Edit

Estimate

ESTIMATE_VERIFIER

Estimate Verifier

Inbox Search View Verify and Forward Send Back

Estimate

TECHNICAL_SANCTIONER

Technical Sanctioner

Inbox Search View Technically Sanction Send Back Send Back To Originator Reject

Estimate

ESTIMATE_APPROVER

Estimate Approver

Inbox Search View Approve Send Back Send Back To Originator Reject

Estimate

WORK_ORDER_CREATOR

Work Order Creator

Inbox Create Search View Edit

Contract

WORK_ORDER_VIEWER

Work Order Verifier

Inbox Search View Verify and Forward Send Back

Contract

WORK_ORDER_APPROVER

WOrk Order Approver

Inbox Search View Approve Send Back Send Back To Originator Reject

Contract

MUSTER_ROLL_VERIFIER

Muster Roll Verifier

Inbox Search View Edit Verify and Forward Send Back

Muster Roll

MUSTER_ROLL_APPROVER

Muster Roll Approver

Inbox Search View Approve Send Back

Muster Roll

MUKTA_ADMIN

MUKTA Admin

Create Organization Search Organization View Organization Modify Organization Search Wage Seeker View Wage Seeker Modify Wage Seeker

Masters

HRMS_ADMIN

HRMS Admin

Create Employee Search Employee View Employee Modify Employee

Employee Users

STADMIN

Dashboard Viewer

Mukta Dashboard

ORG_ADMIN

CBO Admin

all actions of CBO portal

CBO Portal

BILL_CREATOR

Bill Creator

Inbox Search View Create

Billing

BILL_VIEWER

Bill Viewer

Inbox Search View

Billing

EMPLOYEE_COMMON

Common Role For all employee

This role will have all common access that employee should have like edit profile, get Workflow status etc

Common

ESTIMATE_VIEWER

Estimate Viewer

View

Estimate

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

Wage Seeker

Introduction

Wage seekers are the people who are looking for employment and willing to work on MUKTA works.

Data Table

Sr. No.

Aadhaar

Name

Father/ Husband Name

Relationship*

Date of Birth*

Gender

Social Category

Mobile Number

Skill Category

Skill

Pincode

City*

Ward*

Locality*

Street Name

Door/ House No.

Account holder's name*

Account number*

IFSC*

Sunil

Kamlesh

Father

01/03/1991

Male

OBC

7007099196

759001

Dhenkanal

Ward 1

Mahisapat

101/A/01

Sunil

041401518941

ICIC0000047

Vishwash

Kumar N

Father

01/03/1991

Male

OBC

7007099196

759001

Dhenkanal

Ward 1

Bankual

101/A/02

Vishwash

041401518942

ICIC0000047

Karunesh

Varunesh P

Father

01/03/1991

Male

OBC

7007099196

759001

Dhenkanal

Ward 1

Ichhadeipur

101/A/03

Karunesh

041401518943

ICIC0000047

Ramesh

Mayank

Father

01/03/1991

Male

OBC

7007099196

759001

Dhenkanal

Ward 1

Bhagabanpur

101/A/04

Ramesh

041401518944

ICIC0000047

Anjali

Belram

Husband

01/03/1991

Female

GEN

7007099196

759001

Dhenkanal

Ward 1

Mahisapat

101/A/05

Anjali

041401518945

ICIC0000047

Rekha

Sheshkumar

Husband

01/03/1991

Female

7007099196

759001

Dhenkanal

Ward 1

Bankual

101/A/06

Rekha

041401518946

ICIC0000047

Suresh

Mahesh

Father

01/03/1991

Male

7007099196

759001

Dhenkanal

Ward 1

Ichhadeipur

101/A/07

Suresh

041401518947

ICIC0000047

Maheeni

Kankoj

Father

01/03/1991

Male

7007099196

759001

Dhenkanal

Ward 1

Bhagabanpur

101/A/08

Maheeni

041401518948

ICIC0000047

Mehndi

Basantkumar

Father

01/03/1991

Female

OBC

7007099196

759001

Dhenkanal

Ward 1

Mahisapat

101/A/09

Mehndi

041401518949

ICIC0000047

Aslam

Rajesh M

Father

01/03/1991

Male

OBC

7007099196

759001

Dhenkanal

Ward 1

Bankual

101/A/10

Aslam

041401518950

ICIC0000047

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

Organization

Introduction

The enties which are working for the MUKTA schemes like supervision of work, supply of materials etc. are known as organization the ULBs maintained the registries of them.

Data Table

Sr. No.

Organization name*

Name of the department organization is registered with

Department registration number

Date of incorporation* (DD/MM/YYYY)

Organization type*

Orgaization sub type*

Functional category*

Class/ Rank*

Valid From* (DD/MM/YYYY)

Valid To (DD/MM/YYYY)

City*

Ward*

Locality*

Street Name

Door/ House No.

Contact Person Name*

Contact Person Mobile*

Contact Person Email

Account holder's name*

Account number*

IFSC*

PAN*

GSTIN**

Mission Shakti Group

Mission Shakti

NM-101/A-0231/1231

01/04/2020

Community Based Organization

Area Level Federation

Not Applicable

01/04/2021

Jatni

Ward1

MG Road

Asha Devi

8762134510

Mission Shakti Group

1000010342151

UBI00171231

KNSPD7109N

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

Payment Advice Format

Introduction

This the template to generate the payment advice from the system. After downloading the data accountant will be able to proceed with payments in IFMS system.

Data Table

Sr. No.

Project ID

Work Order ID

Bill Number

Bill Type

Gross Amount

Beneficiary Type

Beneficiary Name

Beneficiary ID

Account Type

Bank Account Number

IFSC

Payable Amount

PB/2023-24/000001

Purchase

1010

ORG

1000

PB/2023-24/000001

Purchase

1010

ULB

SB/2023-24/000002

Supervision

900

ORG

900

WB/2023-24/00001

WAGE

100

IND

WB/2023-24/00001

WAGE

200

IND

WB/2023-24/00001

WAGE

300

IND

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

Schedule of rates

Introduction

Schedule of rates are the items used to estimate civil works. The schedule is common across all the ULBs in a state while the rates specific to a ULB.

Data Table

Code

Type

Sub Type

Variant

Description

UOM

Quantity

Material Rate

Labour Rate

Machinery Rate

Conveyance

Royalty

Labour Cess

Total

FL00001

Works

Flooring

Ground Floor

Fixing tiles in floors, treads or steps and landing over 25mm bed of C:M (1:1) jointed with neat cement slurry mixed with pigment to match the shade of the tiles including rubbing and polishing complete excluding the cost of pre-cast tiles

SQM

1307.80

3598.02

66.01

4.55

49.76

5026.14

CC00001

Works

Cement Concrete

Ground Floor

P.C.C. Grade M25 Using Batching plant, Transit Mixer and concrete pump (Data for 120.00 Cum)

CUM

120

329935.45

7095.84

49760.82

32001.01

15930

4347.23

439070.35

CC00002

Works

Cement Concrete

First Floor

P.C.C. Grade M25 Using Batching plant, Transit Mixer and concrete pump (Data for 120.00 Cum) [First Floor]

CUM

120

329935.45

7095.84

49760.82

32001.01

15930

4347.23

439070.35

LD00002

Labour

Un Skilled

Not Applicable

Survey Khalasi/ Chain Man

Nos

345.00

The data given in the table is sample data for reference.

Data Definition

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the SOR.

Type

Text

256

Yes

SOR Type

Sub Type

Text

256

SOR Sub Type

Variant

Text

256

SOR Variant

Description

Text

1024

Yes

SOR Description

UOM

Text

Yes

Unit of measurement

Quantity

Numeric

(6,0)

Yes

Quantity for which rate is defined

Material Rate

Numeric

(6,2)

Rate

Labour Rate

Numeric

(6,2)

Rate

Machinery Rate

Numeric

(6,2)

Rate

Conveyance

Numeric

(6,2)

Rate

Royalty

Numeric

(6,2)

Rate

Labour Cess

Numeric

(6,2)

Rate

Attachments

Ward Boundary

Introduction

Wards are the smallest administrative boundaries with the ULBs. A ULB is divided into multiple wards.

Data Table

Sr. No.

Ward Code

Ward Name

Ward Name (Odia)

W001

Ward 1

ୱାର୍ଡ ୧

W002

Ward 2

ୱାର୍ଡ ୨

W003

Ward 3

ୱାର୍ଡ ୩

W004

Ward 4

ୱାର୍ଡ ୪

W005

Ward 5

ୱାର୍ଡ ୫

W006

Ward 6

ୱାର୍ଡ ୬

W007

Ward 7

ୱାର୍ଡ ୭

W008

Ward 8

ୱାର୍ଡ ୮

W009

Ward 9

ୱାର୍ଡ ୯

W010

Ward 10

ୱାର୍ଡ ୧୦

W011

Ward 11

ୱାର୍ଡ ୧୧

W012

Ward 12

ୱାର୍ଡ ୧୨

W013

Ward 13

ୱାର୍ଡ ୧୩

W014

Ward 14

ୱାର୍ଡ ୧୪

W015

Ward 15

ୱାର୍ଡ ୧୫

W016

Ward 16

ୱାର୍ଡ ୧୬

W017

Ward 17

ୱାର୍ଡ ୧୭

W018

Ward 18

ୱାର୍ଡ ୧୮

W019

Ward 19

ୱାର୍ଡ ୧୯

W020

Ward 20

ୱାର୍ଡ ୨୦

W021

Ward 21

ୱାର୍ଡ ୨୧

W022

Ward 22

ୱାର୍ଡ ୨୨

W023

Ward 23

ୱାର୍ଡ ୨୩

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

Locality Boundary

Introduction

Localities are the boundaries within the ULB and citizens are mostly familiar with these.

Data Table

Sr. No.

Locality Code

Locality Name

Locality Name (Odia)

L001

Kathagada

କାଠଗଡା

L002

Shyamacharanpur

ଶ୍ୟାମଚରଣପୁର

L003

Refugee Colony

ରିଫ୍ୟୁଜି କଲୋନୀ

L004

Kunjakanta

କୁଞ୍ଜକାନ୍ତ

L005

Gudia nali

ଗୁଡ଼ିଆ ନାଲି

L006

Chandamari Sahi

ଚନ୍ଦାମାରୀ ସାହି

L007

Rathagada

ରଥାଗଡା

L008

Danda sahi

ଦଣ୍ଡା ସାହି

L009

Manhisapat

ମନହିଷପାଟ

L010

Banamaliprasad

ବନମାଳିପ୍ରସାଦ

L011

Colony Sahi

କଲୋନୀ ସାହି

L012

Malhar Sahi

ମାଲହର ସାହି

L013

Muslm Basti

ମୁସଲିମ୍ ବସ୍ତି

L014

Kumbhara sahi

କୁମ୍ଭାର ସାହି

L015

Housing Board Colony

ହାଉସିଂ ବୋର୍ଡ କଲୋନୀ

L016

Jagannath Road

ଜଗନ୍ନାଥ ରୋଡ୍

L017

Sasan Chaka

ଶାସନ ଛକ

L018

Jaygopal Sahi

ଜୟଗୋପାଳ୍ ସାହି

L019

Bhagabanpur

ଭଗବାନ୍ପୁର

L020

Similia

ସିମିଳିଆ

L021

Town Planning

ଟାଉନ୍ ବଜାର

L022

Station Bazar

ଷ୍ଟେସନ୍ ବଜାର

L023

Alasua

ଅଲାସୁଆ

L024

Korian

କୋରିଆ

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

Tenants

Introduction

Tenants are organizations which are taking the responsibilties to perform the functions for an geographical area. In MUKTA these oraganizations are known as ULBs.

Data Table

code

name

description

logoId

imageId

domainUrl

type

twitterUrl

facebookUrl

emailId

OfficeTimings

pincode

city

address

contactNumber

helpLineNumber

Mon - Fri

Sat

name

localName

districtCode

districtName

regionName

ulbGrade

longitude

latitude

shapeFileLocation

captcha

code

ddrName

ddrcode

wsBillHeaderLine1

wsBillHeaderLine2

districtTenantCode

od.jatni

Jatni

CITY

helpdesk.sujog@odisha.gov.in

9.00 AM - 6.00 PM

9.00 AM - 12.00 PM

752050

Jatni

Khordha

WATCO-II

Municipality

85.7058693

20.1703784

Khordha

WATCO,OFFICE OF THE DEPUTY HEAD COMMERCIAL

COMMERCIAL WING, SATYA NAGAR, BBSR-751007

od.jatni

Jatni Municipality

1800 121 6833

od.dhenkanal

Dhenkanal

CITY

helpdesk.sujog@odisha.gov.in

9.00 AM - 6.00 PM

9.00 AM - 12.00 PM

759001

Dhenkanal

Angul

Municipality

85.5972218

20.6503455

Dhenkanal

OFFICE OF THE AE/JE

PUBLIC HEALTH ENGINEERING ORGANIZATION : Dhenkanal

od.dhenkanal

Dhenkanal Municipality

1800 121 6833

The data given in the table is sample data for reference.

Data Definition

Sr. No.

Column Name

Data Type

Data Size

Is Mandatory?

Definition/ Description

Code

Alphanumeric

Yes

A unique code that identifies the project type.

Project Type

Text

256

Yes

Provides the name of the project type

Project Type (Odiya)

Text

256

Project type name in local language

Effective From

Date from which the project is effective

Effective To

Date till which the project is effective

Is Active

Whether the project is active or not

Attachments

Measurement

Overview

This module helps in taking the measurement, for an accepted contract

This module has 5 associated screens :

Create
Inbox
Edit
View
Search

Module enablement configuration

Set module code as "Measurement" in Module.js of Measurement Module. Refer https://github.com/egovernments/works-mdms-data/blob/DEV/data/pg/tenant/citymodule.json

{
        "module": "Measurement",
        "code": "Measurement",
        "active": true,
        "order": 13,
        "tenants": [
            {
                "code": "pg.cityb"
            },
            {
                "code": "pg.cityc"
            },
            {
                "code": "pg.citya"
            }
        ]
}

Enable Module in App.js. Update the object ‘enabledModules’. Use the code “Measurement”. This code should match with the code of the cityModule.json, mentioned above.

Role-action mapping

S.No

API

Action ID

Roles

to be updated

MB_CREATOR

to be updated

MB_VERIFIER

to be updated

104

MB_APPROVER

/egov-hrms/employees/_search

EMPLOYEE_COMMON

/inbox/v2/_search

EMPLOYEE_COMMON

Sidebar configuration

S.No

Screen

Navigation URL

LeftIcon Updates

Roles

to be updated

{
      "id": 59,
      "name": "MEASUREMENT",
      "url": "url",
      "displayName": "MEASUREMENT Inbox",
      "orderNumber": 2,
      "parentModule": "",
      "enabled": true,
      "serviceCode": "ATTENDENCEMGMT",
      "code": "null",
      "navigationURL": "/works-ui/employee/measurement/inbox",
      "path": "4MEASUREMENT.Inbox",
      "leftIcon": "dynamic:AttendanceIcon"
}

Document Configuration

https://github.com/egovernments/egov-mdms-data/commit/85761f2c82ced17a0259e077f6b82355e62ce35c

Screen configuration

S.No

Screen

Configuration

to be updated

Inbox

to be updated

Localization Configuration and Modules

TenantID

Module

statea

rainmaker-measurement

Workflow Configuration

UI Component Name

Business Service

WorkflowActions

Custom Components

MeasureTable:

This is the main component that handles the Logic for capturing the measurement for SOR / NONSOR based on the given processed Line items from the Estimate.

The same component has been used in the Detailed estimate which captures the detailed measurement information

The same component has the capability to be used in both create and view screens.

MeasureCard:
This component handles the logic of the inner table present inside the MeasureTable.

IFMS Adapter UI

UI Tech Documentation for JIT

JIT stands for Just in Time e-Payment. We are utilizing JIT in MUKTASOFT for payments.

We have the following screens for JIT in Web-Interface

Search Payment Instruction
View Payment Instruction
Create Payment Instruction (Temporary Screen)

Create Payment Instruction (Temporary Screen)

Payment Instructions are created at the Backend when a bill gets approved. This is handled via cron jobs. We have kept a temporary flow for a user to create Payment for testing cases, or for when cron jobs are not running at Backend properly. In production this flow will be disabled.

To create Payment Instruction from UI. Navigate to Search Payment Instruction screen from home screen card and click on Create Payment Instruction. Search bill screen is opened, the user can select for which bills payment has to be created and click on Generate payment. A relevant toast message is displayed.

Search Payment Instruction

gate, login and go to the Home Page. Then click on Payment Instruction on Mukta Home page card
This screen is utilized to search payments. It has 2 tabs.
- Pending For Action -> This tab will, by default, show all the payments that are either in FAILED or PARTIAL state
- Open Search -> This screen can be utilized to search any payment
Mdms Configs for Search Screen -> Search Payment Instruction
Payment Instruction type config -> Payment Instruction Type
Payment Instruction Status config -> Payment Instruction Status

View Payment Instruction

Users can navigate to the view payment instruction screen from the search payment instruction screen. It shows detailed information about the payment, Beneficiary, and list of payment instructions associated.

Sometimes payment gets failed or partially successful. For these use cases we have two options which are as follows :

For FAILED payments : If a payment is in a failed state, an action button is shown on the view screen to take a retry action. Upon retrying, a new payment instruction gets generated and a toast message is displayed. Also the View screen is refreshed which now includes the newly created payment instruction in INITIATED state.
For PARTIAL payments : If a payment is in PARTIAL state. This basically means payment for at least one beneficiary was successful. In this case we have an option to generate a revised payment instruction which creates a new child payment instruction associated with the original payment instruction. Again, a success toast is displayed and the View screen gets refreshed with newly generated payment instruction. Newly generated payment instruction is now referred to as revised payment instruction.

List of statuses available for payment

Mdms config -> Payment Status

INITIATED
APPROVED
FAILED
INPROCESS
SUCCESSFUL
PARTIAL
COMPLETED

List of Payment Types

Mdms config -> Payment Types

Original
Revised

API's Used for JIT in UI

/wms/ifms-pi/_search -> for Searching PI's
/ifms/pi/v1/create -> For Retry and Partial action

Sample Curl's:

curl 'https://works-qa.digit.org/ifms/pi/v1/_create?_=1693813763900' \
  -H 'authority: works-qa.digit.org' \
  -H 'accept: application/json, text/plain, */*' \
  -H 'accept-language: en-US,en;q=0.9' \
  -H 'content-type: application/json' \
  -H 'cookie: __cuid=59fd9aac25b044f6af006bd4b159cbbf; amp_fef1e8=f4fc07f6-3fb0-4c67-8114-a1beb906e625R...1h2nk91dr.1h2nk91du.a.0.a' \
  -H 'origin: https://works-qa.digit.org' \
  -H 'referer: https://works-qa.digit.org/works-ui/employee/expenditure/view-payment?tenantId=pg.citya&paymentNumber=EP/0/2023-24/09/04/000172' \
  -H 'sec-ch-ua: "Chromium";v="116", "Not)A;Brand";v="24", "Google Chrome";v="116"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Windows"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-origin' \
  -H 'user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36' \
  --data-raw '{"tenantId":"pg.citya","referenceId":"EP/0/2023-24/09/04/000172","RequestInfo":{"apiId":"Rainmaker","authToken":"fb30f563-c053-46e2-acfd-6e1ebdf75827","msgId":"1693813763900|en_IN","plainAccessRequest":{}}}' \
  --compressed

curl 'https://works-qa.digit.org/wms/ifms-pi/_search' \
  -H 'authority: works-qa.digit.org' \
  -H 'accept: application/json, text/plain, */*' \
  -H 'accept-language: en-US,en;q=0.9' \
  -H 'content-type: application/json' \
  -H 'cookie: __cuid=59fd9aac25b044f6af006bd4b159cbbf; amp_fef1e8=f4fc07f6-3fb0-4c67-8114-a1beb906e625R...1h2nk91dr.1h2nk91du.a.0.a' \
  -H 'origin: https://works-qa.digit.org' \
  -H 'referer: https://works-qa.digit.org/works-ui/employee/expenditure/search-payment-instruction' \
  -H 'sec-ch-ua: "Chromium";v="116", "Not)A;Brand";v="24", "Google Chrome";v="116"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Windows"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-origin' \
  -H 'user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36' \
  --data-raw '{"inbox":{"moduleSearchCriteria":{"tenantId":"pg.citya","status":["PARTIAL","FAILED"]},"tenantId":"pg.citya","limit":10,"offset":0},"RequestInfo":{"apiId":"Rainmaker","authToken":"fb30f563-c053-46e2-acfd-6e1ebdf75827","userInfo":{"id":444,"uuid":"bff9c3f6-6a25-45c4-b7ae-dddc016598fd","userName":"SMS QA testing","name":"SMS QA testing","mobileNumber":"9043685314","emailId":"","locale":null,"type":"EMPLOYEE","roles":[{"name":"HRMS Admin","code":"HRMS_ADMIN","tenantId":"pg.citya"},{"name":"WORK_ORDER_VIEWER","code":"WORK_ORDER_VIEWER","tenantId":"pg.citya"},{"name":"BILL_ACCOUNTANT","code":"BILL_ACCOUNTANT","tenantId":"pg.citya"},{"name":"WORK ORDER CREATOR","code":"WORK_ORDER_CREATOR","tenantId":"pg.citya"},{"name":"ESTIMATE VERIFIER","code":"ESTIMATE_VERIFIER","tenantId":"pg.citya"},{"name":"BILL_VERIFIER","code":"BILL_VERIFIER","tenantId":"pg.citya"},{"name":"ESTIMATE APPROVER","code":"ESTIMATE_APPROVER","tenantId":"pg.citya"},{"name":"Organization viewer","code":"ORG_VIEWER","tenantId":"pg.citya"},{"name":"WORK ORDER VERIFIER","code":"WORK_ORDER_VERIFIER","tenantId":"pg.citya"},{"name":"PROJECT VIEWER","code":"PROJECT_VIEWER","tenantId":"pg.citya"},{"name":"BILL_APPROVER","code":"BILL_APPROVER","tenantId":"pg.citya"},{"name":"MUSTER ROLL VERIFIER","code":"MUSTER_ROLL_VERIFIER","tenantId":"pg.citya"},{"name":"OFFICER IN CHARGE","code":"OFFICER_IN_CHARGE","tenantId":"pg.citya"},{"name":"PROJECT CREATOR","code":"PROJECT_CREATOR","tenantId":"pg.citya"},{"name":"Employee Common","code":"EMPLOYEE_COMMON","tenantId":"pg.citya"},{"name":"BILL_VIEWER","code":"BILL_VIEWER","tenantId":"pg.citya"},{"name":"TECHNICAL SANCTIONER","code":"TECHNICAL_SANCTIONER","tenantId":"pg.citya"},{"name":"BILL_CREATOR","code":"BILL_CREATOR","tenantId":"pg.citya"},{"name":"MUSTER ROLL APPROVER","code":"MUSTER_ROLL_APPROVER","tenantId":"pg.citya"},{"name":"ESTIMATE VIEWER","code":"ESTIMATE_VIEWER","tenantId":"pg.citya"},{"name":"WORK ORDER APPROVER","code":"WORK_ORDER_APPROVER","tenantId":"pg.citya"},{"name":"ESTIMATE CREATOR","code":"ESTIMATE_CREATOR","tenantId":"pg.citya"},{"name":"State Dashboard Admin","code":"STADMIN","tenantId":"pg.citya"},{"name":"MUKTA Admin","code":"MUKTA_ADMIN","tenantId":"pg.citya"}],"active":true,"tenantId":"pg.citya","permanentCity":null},"msgId":"1693813698339|en_IN","plainAccessRequest":{}}}' \
  --compressed

User Roles Required for JIT

Roles related to Bill accountant are used here:

Role

Role Code

Access

Bill Accountant

BILL_ACCOUNTANT

Search PI Screen, View PI Screen, Retry and Generate Revised PI Access

Bill Creator

BILL_CREATOR

Search PI Screen, View PI Screen, Retry and Generate Revised PI Access

Rate Analysis

Rate Analysis frontend tech document

Overview

The Rate analysis Module helps in creating rate analysis for Works type of SOR, and helps in bifurcating the rate and revision of rates.

The module has 5 associated screens :

Create Rate Analysis
View Rate Analysis
Edit Rate Analysis

Configurations

MDMS Configurations

S.No.

Data

MDMS Link

SOR Data

Overheads

Module Enablement Configuration

Set module code as “RateAnalysis” in Module.js of Rate Analysis Module. Refer to the file citymodule

{
        "module": "RateAnalysis",
        "code": "RateAnalysis",
        "active": true,
        "order": 15,
        "tenants": [
            {
                "code": "pg.cityb"
            },
            {
                "code": "pg.cityc"
            },
            {
                "code": "pg.citya"
            }
        ]
    }

Enable Module in App.js. Update the object ‘enabledModules’. Use the code RateAnalysis. This code should match the code of the cityModule.json, mentioned above. Role-action Mapping

S.No.

API

Action ID

Roles

/mdms-v2/v2/_create/WORKS-SOR.Composition

MDMS_STATE_ADMIN

/mdms-v2/v2/_update/WORKS-SOR.Composition

MDMS_STATE_ADMIN

/rate-analysis/v1/_calculate

ESTIMATE_CREATOR, MDMS_STATE_ADMIN

Sidebar Configuration

S.No.

Screen

Navigation URL

Left Icon Updates

Roles

Rate Analysis

/workbench-ui/employee/workbench/mdms-search-v2?moduleName=WORKS-SOR&masterName=Composition

dynamic:=ContractIcon

MDMS_STATE_ADMIN, MDMS_CITY_VIEW_ADMIN

Sample object for a sidebar action defined in MDMS (containing navigationUrl )


   {
      "id": 192,
      "name": "MDMS",
      "url": "url",
      "displayName": "Manage Works SOR Composition",
      "orderNumber": 1,
      "parentModule": "",
      "enabled": true,
      "serviceCode": "MDMS",
      "code": "null",
      "navigationURL": "/workbench-ui/employee/workbench/mdms-search-v2?moduleName=WORKS-SOR&masterName=Composition",
      "path": "9MDMS.WORKS-SOR.Composition",
      "leftIcon": "dynamic:ContractIcon"
    }

Screen Configuration

S.No.

Screen

Configuration

Create Rate Analysis

View Rate Analysis

Localization Configuration & Modules

TenantID

Module

rainmaker-common

rainmaker-rateanalysis

rainmaker-common-masters

Workflow Configuration

There is no workflow associated with the Rate Analysis, Only create, view and update screens are present, once the Rate Analysis is created, Users can View and edit the composition.

Customisation

Custom Components used in Rate Analysis:

SORDetailsTemplate - This Component is used to search the SOR and add it in the template but mentioning the quantity of each basic sors.
ExtraCharges - This Component is used to add the additional charges which is not present in the form of basic sors.
TableWithOutHead - This Component is used to show the total value of data with total LC and per unit cost.
RateCardWithRightButton - This Component is used to show the composition data with its rate value
RateAmountGroup - This Component is used to show the Existing rate and new rate for the particular works sor.
ExtraChargesViewTable - This Component is used to show the additional charges added during the creation of composition.

Create/ Edit Rate Analysis Screen:

Use the common Utility “useCustomAPIHook” to gather the data needed for validation and composition creation.
Use the common Utility “getDefaultValues” to gather the init state of the create form.
Pass the createState dependencies to the formComposer.
Refer to docs for Pre-Process config in Component comments.
Figures and additional details is captured in the screen.

View Rate Analysis Screen:

Use the common Utility “useViewRateAnalysisDetails” to gather the data to show from the calculate API of rate analysis.
Call the "viewRateAnalysisdataconfig" to render the view config for the rate analysis according to the dynamic data recieved
Pass the config in the "ViewComposer" to show the segregation of the data according to different heads of Rates.

Muster Roll (CBO Application)

Muster Roll Tech Document

Overview

This module helps in viewing and updating the muster rolls.

ROLE: ORG_ADMIN

This module has 2 associated screens :

View Muster Rolls Inbox
Muster Roll Table Screen

MDMS Configurations

S.No.

Data

MDMS Link

AttendanceHours

WageSeekerSkills

Sent Back to CBO

Based on the business workflow state set for Muster Roll ( Sent BAck for Correction) in respective environments, Add the corresponding code in Sent Back to CBO Code MDMS

User actions

On this page, the following actions need to be performed: If the muster roll is in workflow, User can only view the muster roll, If the muster roll is sent back to CBO,then user can edit the attendance and resubmit the muster roll,

Validations

If Muster Roll is in Workflow, The screen will only be a view page and Save as Draft and Re-Submit button will not be shown in the screen
Based on the Attendance Hours list, users will be allowed to mark the attendance as Full Day, Half Day, or absent. If the list is of length 2, users will be allowed to mark only Full and Absent, Else, users can mark halfday as well.

API Details

muster-roll/v1/_estimate

{

"musterRoll": {

"tenantId":,

"registerId":,

"startDate":,

"endDate":

}

To get the attendance log for the selected Date range

attendance/log/v1/_create

{"attendance": []}

To log the attendance of the individuals for the week

attendance/log/v1/_update

To update the attendance log of the individuals for Sent Back To CBO Muster Rolls

muster-roll/v1/_search

To check if any existing muster rolls present for the selected week

egov-workflow-v2/egov-wf/businessservice/_search

{

"tenantId":,

"businessServices": “musterRollId”,

}

To check the workflow status of the Muster Roll

DIGIT Components and Custom Components Used

S.No

Component

Path

Description

DigitTable

Custom Table with fixed first column and other columns scrollable

DropDownDialog

A dialog with dropdown options

DateRangePicker

A custom Date Range picker to select a range of the month / year

DigitElevatedButton

An Elevated Submit Button

WorkDetailsCard

Details Card based on DIGIT Figma design

DigitTimeLine

WorkFlow TimeLine component viewing Workflow state, And Assignees Details

Localization Configuration and Modules

TenantID

Module

rainmaker-common

rainmaker-muster

rainmaker-common-masters

rainmaker-workflow

pg.citya

rainmaker-pg.citya

Reference Files

Blocs :

Models :

Repositories:

Screens

SORs and Rates

Overview

This module provides the ability to create SORs and Rates

This module has 5 associated screens :

Create
Edit
View
Search

Workbench

The SORs and some related masters were created using the workbench and MDMS v2.

Refer to the Workbench Release document to enable the Workbench

SOR Schemas

SOR

{
  "id": "fd565798-c000-4053-b5f0-4ef5af179934",
  "tenantId": "pg",
  "code": "WORKS-SOR.SOR",
  "description": "WORKS-SOR.SOR",
  "definition": {
    "type": "object",
    "title": "WORKS_SOR.SOR",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id",
      "sorType",
      "uom",
      "quantity"
    ],
    "x-unique": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      },
      "uom": {
        "type": "string"
      },
      "sorType": {
        "type": "string"
      },
      "quantity": {
        "type": "number"
      },
      "sorSubType": {
        "type": "string",
        "default": "NA"
      },
      "sorVariant": {
        "type": "string",
        "default": "NA"
      },
      "description": {
        "type": "string"
      }
    },
    "x-ui-schema": {
      "ui:order": [
        "sorType",
        "sorSubType",
        "sorVariant",
        "uom",
        "quantity",
        "description",
        "*"
      ],
      "description": {
        "ui:widget": "textarea"
      },
      "ui-autogenerate": {
        "id": "works.sor.number"
      }
    },
    "x-ref-schema": [
      {
        "fieldPath": "sorType",
        "schemaCode": "WORKS-SOR.Type"
      },
      {
        "fieldPath": "sorSubType",
        "schemaCode": "WORKS-SOR.SubType"
      },
      {
        "fieldPath": "sorVariant",
        "schemaCode": "WORKS-SOR.Variant"
      },
      {
        "fieldPath": "uom",
        "schemaCode": "common-masters.UOM"
      }
    ]
  },
  "isActive": true,
  "auditDetails": {
    "createdBy": null,
    "lastModifiedBy": null,
    "createdTime": 1695898033182,
    "lastModifiedTime": 1695898033182
  }
}

SOR Type

{
  "id": "9da79f30-0d7f-4ec8-927a-7151f803fcd5",
  "tenantId": "pg",
  "code": "WORKS-SOR.Type",
  "description": "WORKS-SOR.Type",
  "definition": {
    "type": "object",
    "title": "WORKS-SOR.Type",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "code",
      "active"
    ],
    "x-unique": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string"
      },
      "active": {
        "type": "boolean"
      },
      "description": {
        "type": "string"
      }
    }
  },
  "isActive": true,
  "auditDetails": {
    "createdBy": null,
    "lastModifiedBy": null,
    "createdTime": 1695897163197,
    "lastModifiedTime": 1695897163197
  }
}

SOR Subtype

{
  "id": "6d4b30f2-b489-4f8b-bb02-6b3014750e18",
  "tenantId": "pg",
  "code": "WORKS-SOR.SubType",
  "description": "WORKS-SOR.SubType",
  "definition": {
    "type": "object",
    "title": "WORKS-SOR.SubType",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "code",
      "active",
      "type"
    ],
    "x-unique": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string"
      },
      "type": {
        "type": "string"
      },
      "active": {
        "type": "boolean"
      },
      "description": {
        "type": "string"
      }
    },
    "x-ref-schema": [
      {
        "fieldPath": "type",
        "schemaCode": "WORKS-SOR.Type"
      }
    ]
  },
  "isActive": true,
  "auditDetails": {
    "createdBy": null,
    "lastModifiedBy": null,
    "createdTime": 1695897222499,
    "lastModifiedTime": 1695897222499
  }
}

SOR Variant

{
  "id": "6ea9de1f-f924-4133-8689-1571258b57fe",
  "tenantId": "pg",
  "code": "WORKS-SOR.Variant",
  "description": "WORKS-SOR.Variant",
  "definition": {
    "type": "object",
    "title": "WORKS-SOR.Variant",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "code",
      "active"
    ],
    "x-unique": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string"
      },
      "active": {
        "type": "boolean"
      },
      "description": {
        "type": "string"
      }
    }
  },
  "isActive": true,
  "auditDetails": {
    "createdBy": null,
    "lastModifiedBy": null,
    "createdTime": 1695897273559,
    "lastModifiedTime": 1695897273559
  }
}

UOM

{
  "id": "dc4eee9c-28a0-4c99-b113-d1695d1796d6",
  "tenantId": "pg",
  "code": "common-masters.UOM",
  "description": "common-masters.UOM",
  "definition": {
    "type": "object",
    "title": "common-masters.UOM",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "code"
    ],
    "x-unique": [
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "pattern": "^[A-Za-z]+$"
      },
      "baseUom": {
        "type": "boolean"
      },
      "description": {
        "type": "string",
        "pattern": "^[A-Za-z]+$"
      },
      "uomCategory": {
        "type": "string"
      },
      "conversionFactor": {
        "type": "number",
        "minLength": 2
      }
    },
    "x-ref-schema": []
  },
  "isActive": true,
  "auditDetails": {
    "createdBy": null,
    "lastModifiedBy": null,
    "createdTime": 1692771724255,
    "lastModifiedTime": 1692771724255
  }
}

Rates

{
  "id": "21d86249-65ec-4104-9b8f-ce9deb5ad235",
  "tenantId": "pg",
  "code": "WORKS-SOR.Rates",
  "description": "WORKS-SOR.Rates",
  "definition": {
    "type": "object",
    "title": "WORKS-SOR.Rates",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "sorId",
      "rate",
      "validFrom",
      "amountDetails"
    ],
    "x-unique": [
      "sorId",
      "validFrom"
    ],
    "properties": {
      "rate": {
        "type": "number"
      },
      "sorId": {
        "type": "string"
      },
      "validTo": {
        "type": "string"
      },
      "validFrom": {
        "type": "string"
      },
      "amountDetails": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "type",
            "heads",
            "amount"
          ],
          "properties": {
            "type": {
              "enum": [
                "percentage",
                "fixed"
              ],
              "type": "string"
            },
            "heads": {
              "type": "string"
            },
            "amount": {
              "type": "number"
            }
          }
        }
      }
    },
    "x-ui-schema": {
      "ui:order": [
        "sorId",
        "validFrom",
        "validTo",
        "rate",
        "amountDetails",
        "*"
      ]
    },
    "x-ref-schema": [
      {
        "fieldPath": "sorId",
        "schemaCode": "WORKS-SOR.SOR"
      },
      {
        "fieldPath": "amountDetails.*.heads",
        "schemaCode": "WORKS-SOR.Overhead"
      }
    ]
  },
  "isActive": true,
  "auditDetails": {
    "createdBy": null,
    "lastModifiedBy": null,
    "createdTime": 1696330283758,
    "lastModifiedTime": 1696330283758
  }
}

Overheads

{
  "id": "13f4ee64-0d83-4ff8-9cd2-c166fc410405",
  "tenantId": "pg",
  "code": "WORKS-SOR.Overhead",
  "description": "WORKS-SOR.Overhead",
  "definition": {
    "type": "object",
    "title": "WORKS-SOR.Overhead",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "code",
      "active",
      "validFrom",
      "id",
      "description"
    ],
    "x-unique": [
      "code",
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      },
      "code": {
        "type": "string"
      },
      "type": {
        "enum": [
          "percentage",
          "lumpsum"
        ],
        "type": "string"
      },
      "value": {
        "type": "string"
      },
      "active": {
        "type": "boolean"
      },
      "validTo": {
        "type": "string",
        "format": "date-time"
      },
      "validFrom": {
        "type": "string",
        "format": "date-time"
      },
      "description": {
        "type": "string"
      }
    }
  },
  "isActive": true,
  "auditDetails": {
    "createdBy": null,
    "lastModifiedBy": null,
    "createdTime": 1695898168948,
    "lastModifiedTime": 1695898168948
  }
}

MDMS Role Action Configs

Sample data can be referred from the below sheet

Measurement Book (Mobile Application)

Measurement Book Tech Document

Overview

This module helps in taking the measurement, for an accepted contract

Roles: MB_CREATOR, MB_VERIFIER, MB_APPROVER,MB_VIEWER

This module has 5 associated screens :

Inbox
Create
Edit
Update
Search

Home Screen

This screen renders dynamically based on the user's role mapping. It contains two cards: Measurement Book and Work-order Book. These modules are displayed according to the roles assigned to the logged-in user. If the user has the role of MB Creator, the Work-order card will be visible. Similarly, if the user has the MB_VERIFIER, MB_APPROVER,MB_VIEWER role, the Measurement card will be visible. If the user has both roles, both cards will be displayed.

User Actions in Work Order Inbox

New Measurement Book creation:

Tap the "Create Measurement Book" button on any work order to generate a new measurement book.

Work Order Filter:

Users can filter the work order list by work order number, ward, and CBO name.

Work Order Sorting:

Users have the flexibility to sort the entire list based on the amount or CBO name.

User Actions in Measurement Book Inbox:

Existing Measurement Book view/update:

Users can update/view measurement books by tapping on the Create Measurement Book button of any of the work orders.

Measurement Book Filter:

Users have the flexibility in the application to filter the work-order list based on the Measurement Number, projectId, ward and workflow state.

Measurement Book Sorting:

Users have been given the flexibility to sort the whole list based on the amount, SLA days remaining and workflow state.

Create Measurement Book

To create the new Measurement Book, The user is required to go to the Work-order inbox screen by tapping the work-order card on the home screen. In that screen, multiple work orders assigned to him will be available in the list. He/she can tap on the work order to create a Measurement Book.

Conditions for check before Creating new Measurement Book

There are certain check points are expected to be validated before navigating to create a new Measurement Book screen from the work-order card.

SNo

CheckPoints

MB create?

If the existing MB for the selected work-order is in workflow state

Time Extension is in progress

Revision Estimate is in progress

Above points are approved in state

YES

API specifications for the validation:

SNo.

API

body

Description

{

}

Gives the list of measurements related to the contract Number

Gives the estimate details for the estimate Number

Measurement Book create screen:

This screen contains the below components:

SORs, NON-SORs cards for the current opened screen
The primary detail section contains the previous MB list and the brief description of the MB.
Workflow button

User Action in Measurement Book Screen:

User can fill the measurement of the SORs and NON-SORs associated with Work-order. Image of the worksite can be uploaded by the Measurement book reader as to give proof of work done.

After filling the necessary details , user has been given two options such as Save-as-draft and submit.

if the user does save as draft he has the control to edit it as many time as he wants. once the form is submitted. then He can not edit the application in the same screen.

API Specification for Measurement Book Creation:

SNo

API

body

Description

{"roles":""

"isActive":""

"tenantId":""}

Fetches the HRMS employees

Create new measurement

Measurement Book View/Edit/Update:

In order to update or edit the measurement book, the user has to navigate from home screen to measurement Book Inbox by tapping on the Measurement Book Card. In the MB Inbox Screen he/she can edit or update any measurement book by tapping the Open Measurement Book button.

User Action in Measurement Book Screen:

In this screen use can take the actions:

Verify And Forward
Approve
Send Back
Reject
Edit

API Specification for Measurement Book Update:

SNo.

API

Body

Description

{

}

fetching the measurement book details

updating the current measurement book

egov-workflow-v2/egov-wf/process/_search

{"history":"",

"tenantId":"",

"businessIds":""

}

fetches the workflow for the curent measurement book

DIGIT Components & Custom Components Used:

SNO

Component

Path

Description

Common MB Card

Custom card with key value data binding

Multi line Items

custom component contains the digit card component with multi-line calculation functionalities

Floating Action Card

this component contains the floating action button with showModalBottomSheet functions

DropDownDialog

A dialog with dropdown options

DigitElevatedButton

An Elevated Submit Button

Reference Files/Links :

Blocs:

Models:

Repositories:

Measurement Book repository

Screens:

Measurement screens