Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
ULBs prepare the list of works by inviting the ward members and then go through an approval process duly checking on the allocation of funds available. Once the list is finalized and approved in all aspects, the option to enter the same into the system is provided to enable the ULB users to prepare an estimate for each work and then take the work to the closure completing the other activities in the system.
Each finalized Work in the work list is considered a project and the same is created first to start the work.
Create Project
Employee
Role: Project Admin (JE, AE, ME)
Option is provided to enter the approved/ finalized work from the work list for which an estimate will be prepared and the work will be carried out.
Create Project is developed as per the UI design provided and the attributes listed below.
#
Field
Data Type
Required
Description
1
Date of proposal
Date
Y
A date to be entered by the user, can not be a future date.
2
Project Name
Alphanumeric (32)
Y
Name of the project.
Special Chars allowed { / .- _$@#' }
3
Project Description
Alphanumeric (256)
Y
A brief details of works listed under wish-list.
Special Chars allowed { / .- _$@#' () :}
Project Details
4
Letter Reference
Alphanumeric (32)
N
Usually the Offline File/ Letter Number related to the project
Special Chars allowed { / .- _$@#' }
5
Project Type
Drop-down
Y
6
Target Demography
Drop-down
Y
What is the demography the work is being done. E.g. Slum, Areas inhabited by SC, ST, Minorities.
7
Estimated Cost
Numeric
Y
The pre-estimated cost of the project.
Location Details
8
Geolocation
Co-ordinates
N
Input latitude/ longitude, or the GIS-Map to pin the location. Co-ordinate validation.
9
City
Auto-populated
Y
Name of ULB of the logged in user.
10
Ward
Drop-down
Y
Values are the wards no. and names of logged-in ULB/City.
11
Locality
Drop-down
Y
Values are the locality names of logged-in ULB/City.
Relevant Documents
12
Proposal Document
File Attachment
N
Name of file which is uploaded as an attachment.
13
Finalized Worklist
File Attachment
N
Files can be of type jpg, doc, xls, docx, xlsx, pdf. The documents to be attached are configurable.
14
Feasibility Analysis
File Attachment
N
To add more attachments
15
Others
Textbox
N
To enter the file name
File Attachment
N
To attach the file.
Field-level validations as mentioned in the attribute tables.
Mandatory Fields: <Field Name> can not be empty.
Date of proposal: The date of the proposal can not be a future date.
Project Name:
Project name can only include letters, numbers, and the following special characters: / .- _$@#'
The project name should not be more than 32 characters.
Project Description:
Project name can only include letters, numbers, and the following special characters: / .- _$@#' ():
The project description should not be more than 256 characters.
Letter reference/ Requirement number:
Letter reference can only include letters, numbers, and the following special characters: / .- _$@#'
Letter reference should not be more than 32 characters
Estimated Cost: Estimated Cost can only include numbers.
Geolocation: Entered co-ordinates are not the valid latitude or longitude.
It should be as per the DIGIT standard attachment component/mechanism.
Not applicable.
Submit - On submit following activities are performed.
On successful creation of a project.
The success Page is displayed.
The project record gets saved into the system with the status Finalized.
The project ID is generated in a specified format.
Format for Project ID is PJ/FY/<6digitrunningno.>. Example: PJ/2022-23/000051
6 DIGIT running sequence number is reset to 1 at the start of every financial year.
Project details is available to download in PDF as per the given format. There will be a separate ticket for PDF download.
On Failure
The failure Page is displayed.
Not applicable.
1
Create project is given to the role specified.
2
On save, the record gets saved, the success page is displayed and the respective ID is generated as per the given format.
3
All the validations are taken care.
The list of values mentioned under the masters data section. Please refer the to view the sample data of work type.
Employees users creation and role mapping
Employees
HRMS module to be used to create the employee users and mapping of roles.
Roles are created from the back end and actions are mapped as per role requirements.
Once an employee user is created, an SMS notification is sent to the user with a username and first-time password. The user is asked to reset the password login for the first time.
The user resets the password and then logs in to the system using the username and password.
HRMS is packaged with MUKTA and the HRMS access is provided to MUKAT_ADMIN.
Use the UAT for initial testing. Testing credentials and URLs are available on request.
Once the HRMS is packaged with MUKTA, it is tested thoroughly with MUKTA-specific role and action mapping.
Not applicable
Not applicable
On successful login, the user is taken to Home Page.
On failure due to incorrect credentials, an appropriate message is displayed.
It will take the user to the password reset page.
Not applicable.
1
User creation flows to be tested and validated for working without error
2
Home Page for Employees
Employees
Home page for employees to be developed duly taking care of the MUKTA branding aspect.
Upon login into the system as an employee user, the Home Page is displayed.
The home page is displayed with the below details containing 3 sections.
City Logo and Name
City Selection - to support multi-tenancy.
Language Section - by default selected at the time of login
Logged In Users Icon - To show profile and logout menus.
Solution logo and Name
Menu Tree with search facility.
The area containing MUKTA Card with all the menus displayed in it (modules the user has access to) -
Project - It will lead to Project (Search and Create) form.
Estimates - It will lead to the estimate inbox page.
Works Orders - It will lead to the work orders inbox page.
Organization - It will lead to Organization (Search and Create) Page.
Wage Seeker - It will lead to Search Wage Seeker Page.
eGov branding and build information
It should be a DIGIT standard Home Page that allows configuration based on requests from the implementation.
Not applicable
Not applicable
Menu links of different features.
Not applicable
1
The home page will have one card keeping MUKTA-specific menu links
2
The LHS, menu tree gives the user option to navigate through the menu tree as well.
3
Branding and multi-tenancy aspects are taken care of.
Login Page for Employees
Employees
Login page for employees to access the home page and ensure it conforms to Mukta branding guidelines.
A browser window is opened on the access of the MUKTASoft URL asking below details for login.
1
Background Picture/ Watermark
as per the request
2
MUKTASoft | Odisha
Branding of application
3
Login
4
User Name
Textbox
5
Password
Password Textbox
6
City
Drop-down
7
Continue
8
Forgot Password?
It should follow the DIGIT standard login page format and allow the configurations based on the request from the implementation.
Not applicable.
Not applicable.
On successful login, the user is taken to the home page.
On failure due to incorrect credentials, an appropriate message is displayed.
It will take the user to the password reset page.
Not applicable.
1
The login page is designed as described in the story and its configurations aspect is taken care of.
2
Different actions should be working as described.
Search project by ULB/ employee users.
Employee Role: Project Admin, Project_Viewer
Search Project action has to be configurable and allow mapping with a role on demand.
Search Project is provided to allow the users to search Work and view its details/ create estimates.
#
Field Name
Data Type
Description
1
Ward
Drop-down
List of ward boundaries for logged-in user ULB with search by entering name.
2
Project Type
Drop-down
Values of work type from MDMS configuration.
3
Project Name
Textbox
Project Name
4
Project ID
Textbox
Work identification no. generated for a work in works proposal
6
From Date
Date Picker
Proposal creation date, entered by user while creating works proposal.
7
To Date
Date Picker
Proposal creation date, entered by user while creating works proposal.
At least one parameter is required to perform the search.
Consider From Date and To Date as a Date Range single parameter.
An exact search is performed for the values entered/selected other than Project Name.
For Project Name, fuzzy search is applicable.
In case multiple parameter values are supplied AND are applied for searching record.
The search result is shown as given below.
Pagination is displayed to handle the big result set. 10 records are displayed per page.
The option to download the result set in Excel/ PDF is provided.
#
Field
Data Type
Comments
1
Project ID
Display Only
A hyperlink to open the project details in view mode.
2
Project Name
Display Only
Name of project having project description displayed as tool-tip on mouseover.
4
Location
Display Only
Locality name along with ward name.
5
Estimated Cost
Display Only
The project cost from the project details
All the actions are displayed based on role action mapping and the user role assignment.
Search - It will perform the search based on the values supplied for search parameters and the logic defined.
Clear Search - It will clear the values filled for searched parameters.
Project ID - It will take the user to the View Project Details Page.
Not applicable.
1
Search Parameters/ Search Logic should be as stated in the story above.
2
Search result is shown as described in the story.
3
Pagination is provided to handle more results and 10 records per page is displayed.
Verify and forward estimates
Estimate Verifier
To verify and forward the estimate to the next workflow user - the verify and forward action is provided with a pop-up window to capture the below-given details.
Assignee name - This field is drop-down and non-mandatory. The drop-down displays employees having the role of Technical Sanctioner with their names and the designation. For instance, Mahesh K works as a Municipal Engineer and has the role of technical sanctioner displayed as Mahesh K - Municipal Engineer.
Comments - This is a text and non-mandatory field. Users can add any remarks or comments.
Attach Supporting Document - This is a non-mandatory field. Users can attach and upload supporting documents.
Verify and Forward - This is an action button.
Cancel - This is an action button.
On Verify and Forward,
The pop-up window is closed, a toast success message is displayed and the view estimate page is refreshed.
The action menu is loaded according to the role-action mapping of the currently logged-in user.
The estimate is forwarded to the next user in the workflow and displayed in their inbox.
The workflow state changes accordingly and timelines show the current state of the estimate.
The estimate is removed from the currently logged-in user’s inbox.
Estimate Verifier
Pending for verification
Pending for technical sanction
Verified
On cancel, the pop-up window is closed and the toast cancel message is displayed on the view estimate page.
Toast Success Message:
The estimate is verified and forwarded successfully.
Failure Message:
Verification of estimate failed.
Toast Cancel Message:
Action is cancelled.
Not applicable.
1
Clicking on Verify and Forward moves the estimate to the next user in the flow
2
The pop-up window is closed and the view estimate page is refreshed. Toast success message is displayed.
3
The View Estimate page is refreshed based on the changes in the workflow status and the existing user role.
4
On cancel the pop-up window is closed. A toast cancel message is displayed.
The estimate is a document which is prepared to estimate the amount of work required to complete. The estimate helps the Government in tendering, contracting and measuring the work to release the payment.
Create Estimate
Search Project → Search Result → View Project Details → Create Estimate
Employee Role: Estimate Creator
For each project, an estimate is created to award the work to CBO/ JE.
Create Estimate form is developed as per the UI design provided and the attributes listed below.
S. No.
Field
Data Type
Required
Description
1
Estimate Type
Auto-selected
Y
Options are Original, Revised, Deviated.
2
Project ID
Display Only
Y
Project ID
3
Date of Proposal
Display Only
Y
Date of proposal
4
Project Name
Display Only
Y
Name of the project
5
Project Description
Display Only
Y
Project description
6
Project Details
Tab
Same as View Project Details Page.
7
Estimation Details
Tab
8
Line Items
Grid
Y
To capture SOR/ Non-SOR items.
9
Description
Textbox
Y
The description of SOR/ Non-SOR item.
10
UOM
Drop-down
Y
Unit of measurement from the drop-down.
11
Rate
Numeric
Y
Rate per unit
12
Quantity
Numeric
Y
Quantity estimated
13
Amount
Auto-calculated
Y
Amount calculated, Rate*Quantity.
14
Total
Auto-calculated
Y
Grid total
15
Overheads
Section/ Grid
Y
A grid to add the overheads configured in the system.
16
Overhead
Drop-down
Y
Overhead from the drop-down
17
Percentage/ Lump-sum
Display
Y
Valued from the configuration.
18
Amount
Numeric
Y
Auto-calculated/ user entered based on the configuration
19
Total
Auto-calculated
Y
Grid Total
20
Total Estimated Amount
Auto-calculated
Y
Total Estimated Amount = Line Item Amount + Total of all the overheads/ additions.
21
Labour and Material Analysis
Section
22
Material Cost
Numeric
Y
Cost of material component of the work.
23
Labour Cost
Numeric
Y
Cost of labour component of the work.
24
Relevant Documents
25
Detailed Estimate
File Attachment
Y
DIGIT standard file attachment component, file size 5MB.
Format support doc,docx, xls,xlsx pdf, jpg.
26
Labor Analysis
File Attachment
Y
DIGIT standard file attachment component, file size 5MB.
Format support doc,docx, xls,xlsx pdf, jpg.
27
Material Analysis
File Attachment
Y
DIGIT standard file attachment component, file size 5MB.
Format support doc,docx, xls,xlsx pdf, jpg.
28
Project Design
File Attachment
N
DIGIT standard file attachment component, file size 5MB.
Format support doc,docx, xls,xlsx pdf, jpg.
29
Others
Texbox
N
To capture the file which is to be uploaded.
File Attachment
N
DIGIT standard file attachment component, file size 5MB.
Format support doc,docx, xls,xlsx pdf, jpg.
Field level validations as mentioned in the attribute tables and the in-line validations are displayed.
Amount: “Amount can include numbers only.”
Material Cost: “Material cost includes numbers only.”
Labour Cost: “Labour cost includes numbers only.”
The total Material Cost and Labour Costs should not be more than the Total Estimated Amount.
Validation Message: “Material and labour costs should not be more than the estimated amount.”
DIGIT standard attachment component.
It is configurable at the ULB level, the stories for configuring the workflow are given separately.
The overheads in general being used in estimates are given below.
Royalty on Earth Work - It is user entered value
Supervision Charge - It is calculated and calculated on the line item amount at the rate of 7.5%.
Goods and Service Tax - It is calculated and calculated on the line item amount at the rate of 18%.
Overheads are configurable in the system and configured with its complete definition.
There is a separate ticket for overhead configuration.
The workflow window is displayed to capture the assignee name and the comments for forwarding the estimate.
On Forward -
The success Page is displayed.
The estimate record gets saved into the system, and the workflow state reflects ‘Pending for verification’.
Estimate No. is generated in a specified format, if it is a direct submit.
Format for Estimate No. is ES/FY/<6digitrunningno.>. Example: ES/2022-23/000051
The 6-digit running sequence no. is reset to 1 at the start of every FY.
The estimate is available to download in PDF as per the given format. There will be a separate ticket for PDF download.
In case the system fails to create the record, the Failure Page is displayed.
Not applicable.
1
Overheads are rendered and their values are calculated according to the configuration.
2
On Submit, the estimate gets saved, workflow state changes accordingly, and estimate no. is generated.
View Project Details
Employee
Role: Project Admin, Project_Viewer
To view the detailed saved of a Finalized Work, View Project Details Page is provided.
First, the Project is searched using the Search Project feature and then on click of Project ID View Project Details Page is opened with the below details displayed.
Project ID
Proposal Date
Project Name
Project Description
Project Details
Reference No./ Requirement number
Project Type
Target Demography
Estimated Cost
Location Details
Geolocation
City
Ward
Locality
Action [Modify Project, Create Estimate, View Estimate - Actions displayed within action menu]
Attachments [Proposal File, etc.]
A project for which no estimate was created or the latest created estimate is rejected can only be edited. Else the validation message is displayed.
Out of Create Estimate/ View Estimate, only one action is displayed based on the condition and the role of the logged-in user.
If the estimate is created and in workflow OR approved, View Estimate is displayed.
If no estimate is created OR the latest created estimate is rejected, Create Estimate is displayed.
Not applicable.
Modify Project - It will allow the user to edit the project details.
Create Estimate - It will take the user to create the estimate page.
View Estimate - It will take the user to the view estimate page.
Not applicable.
Fill in and submit estimate details.
Estimate Creators
Estimate Creators will find the On Submit pop-up window to capture the details given below:
Assignee name - This field offers a drop-down and is non-mandatory. The drop-down displays the names of employees having the role of Estimate_Verifier and their Designation. For instance, Suresh K working as Junior Assistant Executive Engineer and having the role of estimate verifier is displayed as Suresh K - Assistant Executive Engineer.
Comments - This field is a text area and is non-mandatory. The field is used to add any remarks or comments in context.
Forward - This is an action button.
Cancel - This is an action button.
The On Forward pop-up window captures the following details:
The submit pop-up window is closed and a toast success message is displayed and the view estimate page is refreshed.
The action menu is loaded according to the role-action mapping of the currently logged-in user.
The estimate is forwarded to the next user in the workflow and shown in its inbox.
The workflow state changes accordingly and timelines show the current state of the estimate.
The estimate is removed from the currently logged-in user’s inbox.
The On Cancel closes the submit pop-up window and displays the toast cancel message on the View Estimate page.
Toast Success Message
The estimate is forwarded successfully.
Failure Message
Forward of estimate failed.
Toast Cancel Message
Action is cancelled.
As mentioned in the story.
Not applicable.
Inbox for Employees
Employees
Role: Estimate_Creator, Estimate_Verifier, Technical_Sanctioner, Estimate_Approver.
Inbox page for employees to be developed duly taking care of the MUKTA branding aspect.
The inbox of employees is divided into 4 sections.
Product Name - MUKTA in this case.
Menu Links
Create Estimate - This link will take the user to the Search Project screen to search the project and create the estimate.
Search Estimate - This link will take the user to the Search Estimate screen to search the estimates and view the details.
Estimate No.
Project ID
Project type
Assigned to me - This filter allows the users to filter the estimates assigned to logged-in users only and display the results accordingly.
Assigned to all - Selected by default this filter allows the users to search and view all the estimates that are pending for action and assigned to the user-specific role.
Ward - Multi-select filter to fetch estimates created for selected projects belonging to the selected ward(s).
Locality - Multi-select filter to fetch estimates created for selected projects belonging to selected locality(ies).
Workflow state - Filter to display the estimates in the selected workflow state.
Estimate No.
Project name
Prepared by
Assignee
Workflow state
Estimated Amount
SLA days remaining
It should be a DIGIT standard Inbox that allows configuration based on requests from the implementation.
Not applicable
Not applicable
Menu Links and Search, Filter Apply and Numbers Hyperlinks.
Not applicable.
For any project, an estimate is prepared and then sent for the approval process. The approval process contains various workflow levels and states associated with those levels.
Estimate preparation for a work, by the Estimate Creator and then its verification and approval by other users (actors) in the workflow.
Edit estimate details.
Estimate Creator
The Edit Estimate action is mapped to the Estimate Creator user role.
It is configurable and can be mapped to other roles too as per requirement.
The estimate which is in a workflow can only be edited. Rejected and approved estimates can not be edited.
Edit Estimate allows the user to edit the below-given estimate details.
Once the estimate is edited, it is re-submitted again for approval process using the Submit action.
Not applicable.
On submit a workflow pop-up window is displayed based on the logged-in user role.
On taking respective workflow action, changes get saved and the estimate is forwarded to the next user in the workflow.
On Cancel, the pop-up window is closed and the submit action is cancelled.
Messages are displayed as per workflow stories.
Modify Project
Search Project → View Project Details → Modify Project Details
Employee Role: Project Admin
Option is provided to modify the project details.
Modify Project form is developed as per the UI design provided and the attributes listed below.
Field-level validations as mentioned in the attribute tables. Same as mentioned in Create Project Story.
A project for which no estimate is created or the latest created estimate is rejected can only be modified. Else the validation message on click of Modify button is displayed.
The estimate is prepared for the project, hence the details can not be modified.
DIGIT standard attachment component to be provided.
No workflow is to be configured for the modification of project details.
Submit: On submit -
The project record gets saved into the system and Success Page is displayed.
Due to some technical reason if modification fails, Failure Page is displayed.
Not applicable.
1
ESTIMATE_CREATOR
Create
Submit
Search
View
Edit/ Re-submit
Junior Engineer/ Assistant Engineer
2
ESTIMATE_VERIFIER
Search
View
Verify and Forward
Send Back
Executive Engineer
3
TECHNICAL_SANCTIONER
Search
View
Technical Sanction
Send Back
Send Back To Originator
Reject
Municipal Engineer
4
ESTIMATE_ APPROVER
Search
View
Approve
Send Back
Send Back To Originator
Reject
Executive Officer/ Municipal Commissioner
5
ESTIMATE_VIEWER
Search
View
MUKTA Cordinator
1
Submit
Estimate Creator
Pending for verification
Submitted
2
Verify and Forward
Estimate Verifier
Pending for verification
Pending for technical sanction
Verified
3
Technical Sanction
Technical Sanctioner
Pending for technical sanction
Pending for approval
Technically Sanctioned
4
Send Back
Estimate Verifier
Pending for verification
Pending for correction
Sent Back
5
Send Back
Technical Sanctioner
Pending for technical sanction
Pending for verification
Sent Back
6
Send Back
Estimate Approver
Pending for approval
Pending for technical sanction
Sent Back
7
Send Back To Originator
<roles having access>
<Current Status>
Pending for correction
Sent Back
8
Edit/ Re-submit
Estimate Creator
Pending for correction
Pending for verification
Re-submitted
9
Approve
Estimate Approver
Pending for approval
Approved
Approved
10
Reject
<any roles having access>
<Current Status>
Rejected
Rejected
Estimate
Edit/ Re-submit
Pending for correction
1
Verify and Forward
Pending for verification
2
Technical Sanction
Pending for technical sanction
1
Approve
Pending for approval
1
1
Roles are created as given provided.
2
Actions are configured based on role-action mapping.
3
Workflow states are defined as provided and the state transition is done accordingly by updating the status appropriately.
1
Project details are displayed as described in the story.
2
Actions are enabled as per the role the logged-in user has.
3
1
Estimate No.
Display Only
Y
2
Estimate Type
Display Only
Y
3
Project ID
Display Only
Y
4
Date of proposal
Display Only
Y
5
Project Name
Display Only
Y
This value is populated from project
6
Project Description
Display Only
Y
This value is populated from project
7
Project Details
Tab/ Display
Same to project view
8
Estimation Details
Tab
9
Line Items
Grid
SOR/ Non-SOR items.
10
Description
Textbox
Y
The description of SOR/ Non-SOR item.
11
UOM
Drop-down
Y
Unit of measurement from the drop-down.
12
Rate
Numeric
Y
Rate per unit
13
Quantity
Numeric
Y
Quantity estimated
14
Amount
Auto-calculated
Y
Amount calculated, Rate*Quantity.
15
Total
Auto-calculated
Y
Grid total
16
Overhead
Section/ Grid
17
Overhead
Drop-down
Y
The values are populated from the configuration
18
Percentage/ Lump-sum
Display
Y
The value is displayed per the configuration.
19
Amount
Auto-calculated
Y
Auto-calculated/ User Entered, based on the configuration.
20
Total
Auto-calculated
Y
Grid Total
21
Total Estimated Amount
Auto-calculated
Y
Total estimated value of the project.
22
Labour and Material Analysis
Section
23
Material Cost
Numeric
Y
Cost of the material component
24
Labour Cost
Numeric
Y
Cost of the labour component
25
Relevant Documents
26
Detailed Estimate
File Attachment
Y
DIGIT standard file attachment component, file size 5MB.
27
Labor Analysis
File Attachment
Y
DIGIT standard file attachment component, file size 5MB.
28
Material Analysis
File Attachment
Y
DIGIT standard file attachment component, file size 5MB.
29
Project Design
File Attachment
N
DIGIT standard file attachment component, file size 5MB.
30
Others
Texbox
N
To capture the file which is to be uploaded.
File Attachment
N
DIGIT standard file attachment component, file size 5MB.
Estimate Creator
Submit pop-up window
Estimate Verifier
Verify and Forward pop-up window
Technical Sanctioner
Technical Sanction pop-up window
Approver
Approval pop-up window
1
Configurable role-based access
2
Only the estimates in workflow can be edited
3
Estimate is opened in editable mode
4
The details given in the table can be edited by user
5
On Submit the estimate is again forwarded to the next user for the approval process
#
Field
Data Type
Required
Description
1
Project ID
Display
Y
2
Proposal Date
Date
Y
A date to be entered by the user, can not be a future date.
3
Project Name
Alphanumeric (32)
Y
Name of the project
Special Chars allowed { / .- _$@#' }
4
Project Description
Alphanumeric (256)
Y
A brief details of works listed under wish-list.
Special Chars allowed { / .- _$@#' ()}
Project Details
5
Letter Reference/ Requirement number
Alphanumeric (32)
N
Usually the Offline File/ Letter Number related to the project
Special Chars allowed { / .- _$@#' }
6
Project Type
Drop-down
Y
The list of values mentioned under the masters data section. Please refer the story to view the sample data of work type.
7
Target Demography
Drop-down
Y
What is the demography the work is being done. E.g. Slum, Areas inhabited by SC, ST, Minorities.
8
Estimated Cost
Numeric
Y
The pre-estimated cost of the project.
Location Details
9
Geolocation
Co-ordinates
N
Input latitude/ longitude, or the GIS-Map to pin the location.
10
City
Auto-populated
Y
Name of ULB of the logged in user.
11
Ward
Drop-down
Y
Values are the wards no. and names of logged-in ULB/City.
12
Locality
Drop-down
Y
Values are the locality names of logged-in ULB/City.
Attachments
13
Proposal Document
File Attachment
N
Name of file which is uploaded as an attachment.
14
Finalized Worklist
File Attachment
N
Files can be of type doc, xls, pdf. The documents to be attached are configurable.
15
Feasibility Analysis
File Attachment
N
To add more attachments
16
Others
Textbox
N
To enter the file name
File Attachment
N
To attach the file.
1
Modify project is given to the role specified.
2
On Submit, the record gets saved.
3
Validations are taken care of.
Submit/ Forward
Estimate Creator
Pending for verification
Re-submit/ Forward
Estimate Creator
Pending for correction
Pending for verification
1
On Submit, the application is forwarded to the next user in the workflow.
2
The pop-up window is closed and the application page is refreshed. A toast success message is displayed.
3
On Cancel closes the pop-up window. A toast cancel message is displayed.
4
Workflow state changes and the view estimate page refreshes based on the logged-in user role.
1
It should be a service-wise inbox for all the employee users.
2
Must follow the DIGIT standard inbox design.
Work order is created for an approved estimate in order to award the work to CBO and then send it for the approval process. The approval process contains various workflow levels and states associated with those levels.
Work order preparation for a work by the Work Order Creator and then its verification and approval by other users (actors) in the workflow.
1
WORK ORDER CREATOR
Create
Search
View
Edit/ Re-submit
Submit
Reject
Junior Engineer/ Assistant Engineer
2
WORK ORDER VERIFIER
Search
View
Verify and Forward
Send Back
Executive Officer
3
WORK ORDER APPROVER
Search
View
Approve
Send Back
Send Back To Originator
Reject
Municipal Engineer
4
CBO ADMIN
Accept
Decline
Community based organization contact person (President/ Secretary)
1
Submit
Work Order Creator
Pending for verification
Submitted
2
Verify and Forward
Work Order Verifier
Pending for verification
Pending for approval
Verified
3
Send Back
Work Order Verifier
Pending for verification
Pending for correction
Sent Back
4
Send Back
Work Order Approver
Pending for approval
Pending for verification
Sent Back
5
Send Back To Originator
<any roles having access>
<Current Status>
Pending for correction
Sent Back
6
Edit/ Re-submit
Work Order Creator
Pending for correction
Pending for verification
Re-submitted
7
Approve
Work Order Approver
Pending for approval
Approved
Approved
8
Reject
<any roles having access>
<Current Status>
Rejected
Rejected
9
Accept
CBO Admin
Approved
Accepted
Accepted
10
Decline
CBO Admin
Approved
Pending for re-assignment
Declined
11
Edit/ Re-submit
Work Order Creator
Pending for re-assignment
Pending for verification
Re-submitted
Work Order
Edit/ Re-submit
Pending for correction
1
Edit/ Re-submit
Pending for re-assignment
1
Verify and Forward
Pending for verification
2
Approve
Pending for approval
1
Accept
Approved
7
UI design is going to be the same as the estimate workflow. Only the workflow states will be displayed as per the table given above.
1
Actions are configured based on role-action mapping.
2
Workflow states are defined as provided and the state transition is done accordingly.
Edit Work Order action is to be mapped with Work Order Creator.
It is configurable and can to mapped with other roles too on demand.
The work order which is in the workflow can only be edited.
Rejected, Approved, and Accepted work orders can not be edited.
Edit work orders allows the user to edit the below-given work order detail.
1
Work order number
Display Only
NA
Work order no.
2
Project ID
Display Only
NA
Project ID of the project.
3
Date of proposal
Display Only
NA
Date of the proposal from the project.
4
Project name
Display Only
NA
Project name
5
Project description
Display Only
NA
Project description
6
Project Details
Tab
Displayed as per view project details.
7
Estimate Details
Tab
Displayed as per view estimate details.
8
Work Order Details
Tab
9
Name of CBO
Drop-down
Y
The name of the CBO from the organization master maintained at the ULB level. The name is searchable in the drop-down.
10
CBO ID
Display
Y
The CBO ID from the organization registry.
11
Role of CBO
Drop-down
(Auto- selected)
Y
The role of the CBO is decided based on the estimated amount. It is configurable in the system.
IP (Implementation Partner) - If the estimated cost of the works is more than Rs.15 Lakhs
IA (Implementation Agency) - If the estimated cost of the works is up to Rs.15 Lakhs
12
Name of the officer in-charge
Drop-down
Y
The drop-down values are population based on the role assigned. The name is searchable in the drop-down. Name + Designation
13
Designation of officer in-charge
Display
Y
Displayed from the EIS/User’s record saved in the system.
14
Project completion period
Numeric
Y
Number of days work to be completed.
15
Work order amount
Read Only
Y
Total estimated cost of the selected work.
Relevant Documents
Sections
16
BOQ
File Attachment
Y
Allows single file, not greater than 5 MB. Files can be of type doc, xls, pdf, jpg.
17
Labour Analysis
File Attachment
Y
Allows single file, not greater than 5 MB. Files can be of type doc, xls, pdf, jpg.
18
Material Analysis
File Attachment
Y
Allows single file, not greater than 5 MB. Files can be of type doc, xls, pdf, jpg.
19
Terms and conditions
File Attachment
Y
Allows single file, not greater than 5 MB. Files can be of type doc, xls, pdf, jpg.
20
Others
Textbox
N
To capture the file name
21
File Attachment
N
To attach the file file the name entered above in the textbox.
Once the work order is edited, it is re-submitted for approval using the Submit action button.
Not applicable.
Based on the logged-in user role, a workflow pop-up window is displayed on submit.
Work Order Creator
Submit pop-up window
Work Order Verifier
Verify and Forward pop-up window
Approver
Approval pop-up window
On respective workflow action, changes get saved and the work order is forwarded to the next user in the workflow.
On Cancel, the pop-up window gets closed and the action gets cancelled.
Accordingly, the messages are shown.
<To be updated>
1
Role-based access based on configuration.
2
The work order which is in the workflow can only be edited.
3
The work order is opened in editable mode.
4
The details given in the table can be edited by the user.
5
On Submit, the work order is again forwarded to the next user for approval.
Send back the estimate to the previous user for necessary action.
Estimate Verifier, Technical Sanction, Estimate Approver
To send the estimate back to the previous user in the workflow, Send Back action is provided with the below details to be captured.
Comments - This is a text area and non-mandatory. Users can add any remarks/instructions to be passed on to the previous users in the workflow.
Attach Supporting Document - This is the field for document upload and non-mandatory. Users can attach and upload supporting documents as required. I
Send Back - This is an Action button.
Cancel - This is an Action button.
On Send Back
The pop-up window is closed and a toast success message is displayed.
The view estimate page is refreshed and the action menu is loaded according to the role the logged-in user has.
The estimate is sent back to the previous user’s inbox.
Workflow states change as per the flow.
Estimate Verifier
Pending for verification
Pending for correction
Sent Back
Technical Sanction
Pending for technical sanction
Pending for verification
Sent Back
Estimate Approver
Pending for approval
Pending for technical sanction
Sent Back
On cancel, the toast cancel message is displayed on the view estimate page.
Toast Success Message:
The estimate is sent back successfully.
Failure Message:
Sending back of estimate is failed.
Toast Cancel Message:
Action is cancelled.
Not applicable.
1
On send back, the Pop-up window is closed, a toast success message is displayed and the view estimate page is refreshed
2
The estimate is sent back to the previous user in the workflow
3
Workflow state changes based on the role as mentioned in the story above
4
On cancel, the pop-up window is closed and the toast cancel message is displayed
Reject estimates
Employees
To reject an estimate, action is provided to capture the below-given details and reject the estimate.
Comments - This is a text and non-mandatory field. Users can add any remarks or comments.
Attach Supporting Document - Users can attach and upload the required documents.
Reject - This is an action button.
Cancel - This is an action button.
On Reject,
The pop-up window is closed and a toast reject message is displayed.
The estimate page is refreshed. No actions are enabled for the rejected estimate.
The estimate creator is informed about the rejection of the estimate.
Workflow state changes as given below.
<the role having access of reject action>
<Current State>
Rejected
Rejected
On cancel, the toast cancel message is displayed on the view estimate page.
Toast Success Message:
The estimate is rejected successfully.
Failure Message:
Rejection of estimate failed.
Toast Cancel Message:
Action is cancelled.
SMS to the creator’s mobile
Estimate <estimate no.> for the project <project name> of the location <location> is rejected by <username+designation>. For more details, log in to MUKTASoft to view the estimate details.
On reject, the estimate is rejected and the estimate status changes accordingly.
No further actions can be performed on a rejected estimate.
Notification is sent to the estimate creator.
Workflow state changes as mentioned above in the story.
Search estimates enable the users to search a in workflow/ approved estimate to take further action, like creating a work order.
Search an estimate by various ULB employees/users.
Employee
Role: Estimate Creator, Estimate Verifier, Technical Sanctioner, Approver.
Search Estimate - It has to be configurable and allow mapping with a role on demand.
Search Estimate is provided to allow the users to search for an estimate and view its details.
1
Ward
Drop-down
Auto-complete, matching search.
2
Project Type
Drop-down
Project type
3
Project Name
Textbox
Project name.
4
Estimate No.
Textbox
Estimate no.
5
Status
Drop-down
Workflow status of an estimate.
6
From Date
Date Range
Estimate creation date.
7
To Date
Date Range
Estimate creation date.
8
Search
Button
9
Clear Search
Button
At least one parameter’s value is required to perform the search.
The date range From Date/ To Date is considered one parameter.
An exact search is performed for the values entered/selected other than Project Name.
For Project Name, fuzzy search to be provided.
In case multiple parameter values are supplied AND are applied for searching record.
The search result is shown as given below.
Pagination is displayed to handle the big result set. 10 records per page are displayed.
The option to download the result set in Excel/ PDF is provided.
1
Estimate No.
Display Only
A hyperlink to open the estimate in view mode.
2
Project Name
Display Only
Mouseover action on the project name shows the project description as a tooltip.
3
Location
Display Only
Locality name along with ward name. Locality + Ward
4
Prepared By
Display Only
Name of user who has prepared it.
5
Status
Display Only
Status of the estimate.
6
Estimated Amount
Display Only
Total estimated amount.
At least one parameter’s value is required to perform the search.
Search - It will perform the search and display the result. In case, no result is found appropriate message is displayed.
Clear Search - It will clear the search parameters.
Estimate No. - Hyperlink will take the user to the estimate detail page.
Not applicable.
1
At least one parameter is required to perform the search.
2
Search results are displayed on matching records found else no record found message is displayed.
3
Pagination is applied if more than 10 records are found.
Approve estimates
Estimate Approver
For the approval of an estimate, action Approve is provided and the below-given detail is captured in a pop-window on approval.
Comments - This is a text and non-mandatory field. Users can add any remarks or comments.
Attach Supporting Document - This is a non-mandatory field. Users can attach and upload supporting documents.
Approve - This is an action button.
Cancel - This is an action button.
On Approve,
The estimate is approved.
Approve pop-up window is closed, a toast success message is displayed and the view estimate page is refreshed.
Workflow state changes as given below.
Estimate Approver
Pending for approval
Approved
Approved
On cancel, the toast cancel message is displayed.
Toast Success Message:
The estimate is administratively approved successfully.
Failure Message:
Approval of estimate failed.
Toast Cancel Message:
Action is cancelled.
SMS to the estimate creator
Estimate <estimate no.> for the project <projectname> of the location <location> is approved. For more details log in to MUKTASoft to view the estimate details.
1
On approval, estimate workflow state changes accordingly.
2
On approval, a notification is sent to the estimate creator.
Send back estimates to the originator for necessary action.
Employees
This allows the user to send the estimate back to the originator’s inbox for any correction required. Below given detail is captured.
Comments - This is a text area and non-mandatory field. Users can add any remarks/ instructions to be passed to the originator of the estimate.
Attach Supporting Document - This is a document upload field and non-mandatory. Users can attach and upload supporting documents while sending the estimate back to the originator.
Send Back - This is an action button.
Cancel - This is an action button.
On Send Back
The pop-up window is closed and a toast success message is displayed.
The view estimate page is refreshed and the actions menu is loaded according to the role the logged-in user has.
The estimate is moved to the creator’s inbox.
The Edit Estimate option is available to the Estimate Creator to edit the estimate and attached the new documents files and submit it.
Workflow state changes as given below.
<roles having access to send back to originator>
<Current Status>
Pending for correction
Sent Back
Clicking on cancel closes the pop-up window and the toast cancel message is displayed on the view estimate page.
Toast Success Message:
The estimate is sent back to the creator successfully.
Failure Message:
Sending back of estimate failed.
Toast Cancel Message:
Action is cancelled.
Not applicable.
1
The estimate is moved to Estimate Creator’s inbox.
2
Estimate Creator- Edit Estimate action is enabled to edit the estimate.
3
Workflow state changes as mentioned in the ticket.
Technical sanction of estimates.
Employees
To technically sanction the estimate the action Technical Sanction is enabled in the action menu and a pop-up window is opened with the following details.
Assignee name- This is a drop-down field and non-mandatory. The drop-down displays employees having the role of Estimate Approver with their names and the designation. For instance, Rakesh K works as an Executive Officer and has the role of Estimate Approver displayed as Rakesh K - Estimate Approver.
Comments - This is a text and non-mandatory field. Users can add any remarks or comments.
Attach Supporting Document - This is a non-mandatory field. Users can attach and upload supporting documents.
Technical Sanction- This is an action button.
Cancel - This is an action button.
On technical sanction,
The pop-up window is closed, a toast success message is displayed and the view estimate page is refreshed.
The action menu is loaded according to the role-action mapping of the current user.
The application is forwarded to the next user in the workflow and the workflow state changes.
Timelines show the current state of the estimate in the workflow.
Technical Sanction
Pending for technical sanction
Pending for approval
Technically Sanctioned
Clicking on cancel closes the pop-up window and a toast cancel message is displayed on the view estimate page.
Toast Success Message:
The estimate is technically sanctioned successfully.
Failure Message:
Technical sanctioning of estimated failed.
Toast Cancel Message:
Action is cancelled.
Not applicable.
1
On technical sanction, the estimate is forwarded to the next user in the workflow
2
The pop-up window is closed, a toast success message is displayed, and the estimate page is refreshed
3
The View Estimate page is refreshed based on the changes in the workflow status and the logged-in user role.
4
Clicking on cancel closes the pop-up window. A toast cancel message is displayed.
Hence for Work Order Creator, the On Submit pop-up window is opened to capture the below-given details.
Assignee name- Drop-down - Non Mandatory - The next user in the workflow i.e. work order verifier hence the employees having the role Work_Order_Verifier are displayed in drop-down with the Name and Designation. E.g. Suresh K working as Junior Assistant Executive Engineer and having the role of work order verifier will be displayed ‘Suresh K - Assistant Executive Engineer’.
Comments - Text area - Non-Mandatory - In case any comments to be added.
Forward - Action Button
Cancel - Action Button
On Forward,
The pop-up window is closed, a toast success message is displayed and the view work order page is refreshed.
The action menu is loaded according to the role-action mapping of the currently logged-in user.
The work order is forwarded to the next user in the workflow and shown in its inbox.
The workflow state changes accordingly and timelines show the current state of the estimate.
Work order is removed from the currently logged-in user’s inbox.
Submit/ Forward
Work Order Creator
Pending for verification
Submitted
Re-submit/ Forward
Work Order Creator
Pending for correction
Pending for verification
Re-submitted
On cancel, a pop-up window is closed, toast cancel message is displayed on the view work order page.
Toast Success Message:
The work order is forwarded successfully.
Failure Message:
Forward of work order failed.
Toast Cancel Message:
Action is cancelled.
Not applicable.
Not applicable.
1
On submission, the application is forwarded to the next user in the flow.
2
The pop-up window gets closed and the application page is refreshed. A toast success message is displayed.
3
On cancel pop-up window is closed. A toast cancel message is displayed.
4
Workflow states change and based on the role the existing user has view work order page refreshes.
Inbox for Employees
Employees
Inbox page for employees to be developed duly taking care of the MUKTA branding aspect.
The inbox of employees is divided into 4 sections.
Menu Title
Product Name
Menu Links
Create Work Order - It will take the user to the search estimate page.
Search Work Order - It will take the user to search work order.
Search Parameters
Work order number
Project ID
Project type
Filters
Assigned to me - It displays the work orders in the inbox which are assigned to the logged-in user.
Assigned to all - Selected by default, It displays the work orders in the inbox which are pending for action of role(s) logged-in users have.
Ward - Multi-select
Locality - Multi-select
Workflow state - state of the workflow of the work order.
Result Display Area
Work order number
Project name
CBO name
Assignee
Workflow state
Work Order Amount
SLA days remaining
It should be a DIGIT standard Inbox that allows to configure based on a request from the implementation.
Not applicable.
Not applicable.
Menu links and Search, Filter apply and Numbers h.yperlinks.
Not applicable.
1
It should be a service-wise inbox for all the employee users.
2
Following the DIGIT standard inbox design.
View Estimate
Search Estimate → View Estimate.
Employee
Role: All roles applicable to an employee user.
To view the details of the saved Estimate, View Estimate Page is provided.
Estimate is searched using the Search Estimate feature and then on click of Estimate No. view estimate page is opened with the below details displayed.
Estimate No.
Estimate Type
Project ID
Date of Proposal
Project Name
Project Description
Project Details [ The project details are shown as view project detail in a separate TAB]
Estimation Details
Line Items - Below information is displayed in the grid.
Description
UOM
Rate
Quantity
Amount
Total - Grid total.
Overheads - Below information is displayed in the grid.
Overhead
Percentage/ Lump-sum
Amount
Total - Grid Total
Total Estimated Amount
Material and Labour Analysis
Labour Cost
Material Cost
Attachments
Detailed Estimate
Labour Analysis
Material Analysis
Design Document
Timelines [DIGIT standard way of displaying the timelines, refer to wire-frame and as described in workflow story]
Actions - Based on the workflow state and role the logged-in user has.
Not applicable.
Not applicable.
For In Workflow Estimates, actions in the Action Menu, workflow actions based on the role of the logged-in user.
Verify and Forward,
Technical Sanction
Approve
Send Back
Send Back To Originator
Edit Estimate
Reject
For Approved Estimates, actions in the Action Menu, actions based on the role of the logged-in user.
Create Work Order - If the estimate is not created.
View Work Order - If the work order is created and not in Rejected status.
Create Revised Estimate - In V2.
Create Deviation Statement- In V2.
Rejected - No actions/ even action button is not displayed.
Not applicable.
1
Estimate details are displayed as described in the story.
2
Actions are enabled as per the estimated workflow state and role of the logged-in user.
Once an estimate is prepared and approved, the next step is to award the work to a contractor, to decide the various methods used like Tendering, Quotation and Nomination. Once a contractor is decided a work order is created in the favor of the contractor.
In MUKTA, it is a nomination method to decide a CBO (community-based organization) and then the work order is created in the name of that organization.
Create Work Order
Search Estimate → View Estimate → Create Work Order.
Employee
Role: Work Order Creator
CBO to whom the work is awarded is decided offline and then the work order is created in the name of CBO.
Create Work Order form is developed as per the UI design provided and the attributes listed below.
To create the work order estimate is searched and opened to view the details. From the action menu Create Work Order is selected.
#
Field
Data Type
Required
Description
1
Project ID
Display Only
NA
Project ID of the project.
2
Date of proposal
Display Only
NA
Date of the proposal from the project.
3
Project name
Display Only
NA
Project name
4
Project description
Display Only
NA
Project description
5
Work Order Details
Tab
6
Name of CBO
Drop-down
Y
Organization type community based organization from the organization master maintained at the ULB level are only allowed.
Only Active organizations and the organization valid to date is above work order created date are listed under drop-down or allowed to search.
The name is searchable in the drop-down and search is start with min 3 characters has to be entered.
Search is performed for the CBOs registered within the ULB.
7
CBO ID
Display
Y
The CBO ID from the organization registry.
8
Role of CBO
Drop-down
(Auto- selected)
Y
The role of the CBO is decided based on the estimated amount. It is configurable in the system.
IP (Implementation Partner) - If the estimated cost of the works is more than Rs.15 Lakhs
IA (Implementation Agency) - If the estimated cost of the works is up to Rs.15 Lakhs
9
Name of the officer in-charge
Drop-down
Y
The drop-down values are population based on the role assigned.
The name is searchable in the drop-down with min 3 characters entered. Name + Designation;
Search is performed within the employees having the role OFFICER_IN_CHARGE.
10
Designation of officer in-charge
Display
Y
Displayed from the EIS/User’s record saved in the system.
11
Project completion period (in days)
Numeric
Y
Number of days work to be completed.
Min Value: 1 day.
12
Work order amount
Read Only
Y
Total estimated Amount - Overhead Amount (Sum of all which are not a work value)
13
Labour and Material Analysis
14
Labour Analysis
View Document
Y
The labour analysis file attached to estimate to be displayed here.
15
Material Analysis
View Document
Y
The material analysis file attached to estimate to be displayed here.
16
Relevant Documents
Sections
17
BOQs
File Attachment
Y
Allows single file, not greater than 5 MB. Files can be of type doc,docx, xls,xlsx pdf, jpg.
18
Terms and conditions
File Attachment
N
Allows single file, not greater than 5 MB. Files can be of type doc,docx, xls,xlsx pdf, jpg.
19
Others
Textbox
N
To capture the file name
20
File Attachment
N
To attach the file file the name entered above in the textbox.Allows single file, not greater than 5 MB. Files can be of type doc,docx, xls,xlsx pdf, jpg.
21
Terms and Conditions
Tab
22
Description
Alphanumeric
N
Grid of textbox to enter the terms and conditions as bulleted list.
Field-level validations as mentioned in the attribute tables.
Organization-type community-based organizations from the organization master maintained at the ULB level are only allowed.
Only Active and Valid To >= Work Order Created Date, organization are listed under drop-down or allowed to search. The organization with the status “Inactive” and “Debarred” are not listed irrespective of valid to date.
The minimum value for the work completion period should not be less than 1 day.
The Role of CBO drop-down is selected automatically by the system based on the configuration provided.
IF the total estimated amount <=15 lakhs THEN the Role of CBO = IA AND the role can be changed by the user.
IF the total estimated amount is >15 lakhs THEN the Role of CBO = IP AND the role can not be changed by the user.
The amount limit deciding the role of CBO should be configurable. At present it is 15 lakh.
The stories for configuring the workflow are given separately.
On Submit
Submit workflow opens a pop-up window with the Forward option.
The work order record is saved into the system and the workflow state changes to Pending for verification.
The Work Order No. is generated in a specified format, if it is a direct submission.
Format for Work Order No. is WO/FY/<6digitrunningno.>. Example: WO/2022-23/000051
6 DIGIT running sequence number is reset to 1 with the start of the new FY.
The work order is available to download in PDF as per the given format. There will be a separate ticket for PDF download.
On cancel, the action is cancelled.
On successful forward the Success Page is displayed else the Failure Page is displayed.
Not applicable.
1
The role of CBO is decided based on the logic provided.
2
On Forward, the work order is forwarded to the next user.
3
The work order number is generated as per the specified format.
4
On successful forward Success Page is displayed else Failure Page is displayed.
Verify and forward the work order to the next workflow user.
Employees
The Verify and Forward action is provided with a pop-up window to capture the below-given details.
Assignee name- Drop-down - Non Mandatory - The next user in the workflow i.e. Approver, hence the employees having the role Work_Order_Approver are displayed in drop-down with the name and the designation. E.g. Mahesh K working as EO and having the role of Work_Order_Approver will be displayed as ‘Mahesh K - Executive Officer’.
Comments - Text area - Non-Mandatory - In case any comments to be added.
Attach Supporting Document - Non-Mandatory - Any document to be uploaded as a supporting document.
Verify and Forward - Action Button
Cancel - Action Button
The pop-up window is closed, toast cancel message is displayed on the view work order page
On Verify and Forward,
A pop-up window is closed, the toast success message is displayed and the view work order page is refreshed.
The action menu is loaded according to the role-action mapping of the currently logged-in user.
The work order is forwarded to the next user in the workflow and shown in its inbox.
The workflow state changes accordingly and timelines show the current state of the work order.
Work order is removed from the currently logged-in user’s inbox.
Toast Success Message:
The work order has been forwarded successfully.
Failure Message:
Verification of work order failed.
Toast Cancel Message:
Action has been cancelled.
Not applicable.
Reject the work order.
Employees
To reject the work order, action is provided to capture the below-given detail and reject the work order.
Comments - Text area - Mandatory
Attach Supporting Document - Document upload
Reject - Action Button
Cancel - Action Button
On Reject,
The pop-up window is closed, toast reject message is displayed.
The work order page is refreshed. No actions are enabled for the rejected work order.
The work order creator is informed about the rejection of the work order through SMS notification.
Workflow state changes as given below.
3. On cancel, a toast cancel message is displayed on the view work order page.
Toast Success Message:
Work order has been rejected successfully.
Failure Message:
Rejection of work order is failed.
Toast Cancel Message:
Action has been cancelled.
SMS to the creator’s mobile
Work order <work order no.> for the project <project name> of the location <location> has been rejected by <username+designation>. For more detail please login to MUKTASoft to view the work order details.
Send the work order back to the previous user in the workflow.
Employees
Send Back action is provided with the below details to be captured.
Comments - Text area - Non-mandatory - It is provided to add any remarks/instructions to be passed on to the previous user in the workflow.
Attach Supporting Document - Document upload - Non-mandatory - In case any documents are to be attached.
Send Back - Action Button
Cancel - Action Button
On Send Back,
The pop-up window is closed, and a toast success message is displayed.
The view work order page is refreshed and the action menu is loaded according to the role of the logged-in user.
The work order is sent back to the previous user’s inbox.
Workflow states change as per the flow.
On cancel, the toast cancel message is displayed on top of the view work order page.
Toast Success Message:
Work order has been sent back successfully.
Failure Message:
Sending back of work order is failed.
Toast Cancel Message:
Action has been cancelled.
Not applicable.
Employee inbox with links and search filters.
Employees
Inbox for Employees
Menu Links and Search, Filter Apply and Numbers Hyperlinks.
Inbox page for employees to be developed duly taking care of the MUKTA branding aspect.
The inbox of employees is divided into 4 sections.
Menu Title
Product Name
Menu Links
Search Muster Roll - It will take the user to search the muster roll page.
Search Parameters
Muster roll ID
Project ID
Project type
Filters
Assigned to me - It will display the work orders in the inbox which are assigned logged in user.
Assigned to all - Selected by default, It will display the work orders in the inbox which are pending for action of role(s) logged in user have.
Ward - Multi-select
Locality - Multi-select
Workflow state - state of the workflow of the work order.
Result Display Area
Muster roll ID
Project name
CBO name
Assignee
Workflow state
Amount
SLA days remaining
It should be a DIGIT standard inbox that allows configuration based on requests from the implementation.
Not applicable
Not applicable
Not applicable.
Send the work order back to the originator’s inbox for any correction required.
Employees
It is provided to send the work order back to the originator’s inbox for any correction required. Below given detail is captured.
Comments - Text area - Non-mandatory - It is provided to add any remarks/ instructions to be passed to the originator of the work order.
Attach Supporting Document - Document upload - Non-mandatory - In case any documents are to be attached while sending the work order back to the originator.
Send Back - Action Button
Cancel - Action Button
On Send Back -
The pop-up window is closed and a toast success message is displayed.
The view work order page is refreshed and the actions menu is loaded according to the role the logged-in user has.
The work order is placed into the work order creator’s inbox.
The ‘Edit Work Order’ option is provided to Work Order Creator to edit the work order and attached the new documents files and Re-submit it.
Workflow state changes as given below.
On cancel, the pop-up window is closed, toast cancel message is displayed on the view work order page.
Toast Success Message:
Work order has been sent back to the creator successfully.
Failure Message:
Sending back of work order is failed.
Toast Cancel Message:
Action has been cancelled.
Not applicable.
For approval of work order.
Employees
For the approval of the work order, action Approve is provided and the below given detail is captured in a pop-window on approval.
Comments - Text area - Non-mandatory
Attach Supporting Document - Document upload - Non-mandatory
Approve - Action Button
Cancel - Action Button
On Approve,
The work order is approved.
Approve pop-up window is closed, a toast success message is displayed and the view work order page is refreshed.
Workflow timelines are displayed accordingly.
Workflow state changes as given below.
On cancel, the toast cancel message is displayed.
Toast Success Message:
Work order has been administratively approved successfully.
Failure Message:
Approval of work order is failed.
Toast Cancel Message:
Action has been cancelled.
SMS to the Work Order Creator
Work Order <work order no.> for the project <projectname> of the location <location> has been approved and sent to <CBOName> for acceptance. For more detail please login to MUKTASoft to view the estimate details.
SMS to the CBO
Dear <contactpersonname>, <organisationname> has been chosen as the <IA/IP> for the project <project name>. Please accept the work order <WO_NUMBER> before <duedate> to avoid auto cancellation. To login please click on <Organization Login URL>.
Generate a pdf copy of the work order.
Employees
The Work Order PDF has 6 main sections.
Header - Municipality Info and Work Order No. and Amount.
Work order is addressed to either JE/AE or CBO.
The subject section
The content of the work order body
The work order issue detail
Footer - Terms and Conditions
Conditions
In case the CBO role is defined as the Implementation Agency
The work order is addressed to CBO only.
<Officer Incharge/ CBO> ---> <CBO Name>
<Implementation Agency/ Implementation Partner> ---> <Implementation Agency>
In case the CBO role is defined as Implementation Partner
The work order is addressed to JE and CBO both, JE’s name comes first.
<Officer Incharge/ CBO> ---> <Officer In-charge Name>
<Implementation Agency/ Implementation Partner> ---> <Implementation Partner>
Other variables -
SLA Days - maximum days are given to CBO to accept the work order.
Due Date - Work order approval date + SLA Days
View specific work order details.
Employee
Role: Work Order Creator, Work Order Verifier, Work Order Approver.
View Work Order
Search Work Order→ View Work Order
To view the details of the saved Work Order, a View Work Order page is provided.
First the work order is searched using the search Work Order feature and then on click of Work Order No. the view work order page is opened displaying the below details.
Work order number
Project ID
Date of proposal
Project name
Project description
Work Order Details
Name of CBO
Organization ID
Role of CBO
Designation of officer in-charge
Name of the officer in-charge
Project completion period (In days)
Work order amount
Relevant Document
File Attachments - allow to view the documents, on click document is opened to view.
Workflow timelines - As per the designed UI.
Terms and conditions - Terms and conditions are displayed as entered.
For In Workflow Work Order - Workflow actions are based on the role of the logged-in user.
Edit
Verify and Forward
Send Back
Send Back To Originator
Approve
Reject
For accepted WO
Revise Work Order (Time extension only)
Field level validations as mentioned in the attribute tables.
Not applicable.
Not applicable.
Search a work order by various ULB Employees/ users.
Employee
Role: Work Order Creator, Work Order Verifier, Work Order Approver.
Search Work Order- It has to be configurable and is mapped with a role on demand.
Search Work Order is provided to allow the users to search for a work order and view its details.
Search - To search the result upon supplying the values of the parameters.
Clear Search - To clear the search parameters supplied.
At least one parameter is required to perform the search.
The date range From Date/ To Date is considered one parameter.
An exact search is performed for the values entered/selected except the project name.
For project name fuzzy search to be enabled.
In case multiple parameter values are supplied AND are applied for searching record.
The search result is shown as given below.
At least one parameter is required to perform the search.
Not applicable.
Work Order Verifier
Pending for verification
Pending for approval
Verified
1
Verify and forward pushes the work order to the next user in the flow.
2
The pop-up window is closed and the view work order page is refreshed. A toast success message is displayed.
3
Workflow states change, and based on the existing role the user can view the work order page on refresh.
4
On cancel pop-up window is closed. A toast cancel message is displayed.
<the role having access of reject action>
<Current State>
Rejected
Rejected
1
On reject, the work order is rejected and the workflow state/status changes accordingly.
2
No further actions can be performed on a rejected work order.
3
Notification is sent to the work order creator.
Work Order Verifier
Pending for verification
Pending for correction
Sent Back
Work Order Approver
Pending for approval
Pending for verification
Sent Back
1
On send back, the pop-up window is closed and a toast success message is displayed. The view work order page is refreshed.
2
The work order is sent back to the previous user in the workflow and the workflow timeline gets updated.
3
Workflow state changes based on the role as mentioned in the story above.
4
On cancel, the pop-up window is closed and a toast cancel message is displayed.
1
It should be a service-wise inbox for all the employee users.
2
Following the DIGIT standard inbox design.
<roles having access to send back to originator>
<Current Status>
Pending for correction
Sent Back
1
The work order is moved to Work Order Creator’s inbox.
2
Work Order Creator- Edit Work Order action is enabled to edit the work order.
3
Workflow state changes as mentioned in the ticket.
1
Ward
Drop-down
Auto-complete, matching search. The values populated from ward boundary master data.
2
Project type
Drop-down
Project type masters value
3
Project name
Textbox
Project name
4
Work order number
Textbox
Work Order number, unique identification no.
5
Status
Drop-down
Workflow state of a work order.
6
Created From Date
Date Picker
Work Order creation date.
7
Created To Date
Date Picker
Work Order creation date.
1
Work order number
Display Only
A hyperlink to open the work order in view mode.
2
Project name
Display Only
Project name with project description displayed as tool-tip on mouseover
3
Name of CBO
Display Only
Name of the organization to whom Work Order is awarded.
4
Role of CBO
Display Only
Role of CBO, IA/IP
5
Location
Display Only
Locality name along with ward name. (Locality + Ward)
6
Status
Display Only
Workflow status of the work order.
7
Work order amount
Display Only
Total WO amount.
1
At least one parameter is required to perform the search.
2
Search results are displayed on matching records found else no record found message is displayed.
3
Pagination is applied if more than 10 records are found.
Work Order Approver
Pending for approval
Approved
Approved
1
On approve, work order workflow state changes accordingly.
2
On approve, notification is sent to work order creator.
1
Design should be as per Figma.
2
Conditions are fulfilled.
1
Work Order details are displayed as described in the story.
2
Actions are enabled as per the work order workflow state and role the logged-in user has.
Map workflows to roles for muster rolls.
Employees, Admins.
Muster roll is created by CBO weekly and then sent for approval and payment to JE/AE.
1
CBO ADMIN
Create
View
Edit/ Re-submit
Submit
CBO User
2
MUSTER ROLL VERIFIER
Search
View
Edit
Verify and Forward
Send Back To CBO
Junior Engineer/ Assistant Engineer
3
MUSTER ROLL APPROVER
Search
View
Approve
Send Back
Municipal Engineer
1
Submit
CBO ADMIN
Pending for verification
Submitted
2
Verify and Forward
MUSTER ROLL VERIFIER
Pending for verification
Pending for approval
Verified
4
Send Back
MUSTER ROLL APPROVER
Pending for approval
Pending for verification
Sent Back
5
Send Back To CBO
<any roles having access>
<Current Status>
Pending for correction
Sent Back
6
Edit/ Re-submit
CBO ADMIN
Pending for correction
Pending for verification
Re-submitted
7
Edit/ Re-submit
MUSTER ROLL VERIFIER
Pending for verification
Pending for approval
Re-submitted
8
Approve
MUSTER ROLL APPROVER
Pending for approval
Approved
Approved
MUSTER ROLL
Edit/ Re-submit
Pending for correction
1
Edit/ Re-submit
Pending for verification
1
Verify and Forward
Pending for verification
1
Approve
Pending for approval
1
UI design is going to be the same as the estimates workflow. The workflow states will be displayed as per the table given above.
1
Actions are configured based on role - action mapping.
2
Workflow states are defined as provided and the state transition is done accordingly.
Provide users with the option to create wage bills.
Employee
Role: Bill Creator
Bill record gets saved into the system, and attains a workflow state ‘Approved’.
Bill No. is generated in a specified format.
Format for Work Bill No. is WB-FY-<6digitrunningno.>. Example: WB/2022-23/000051
Bill is available to download in PDF as per the given format. There will be a separate ticket for PDF download.
A wage bill is created for the wages paid to wage seekers.
The wage bill is created automatically on approval of the muster roll.
To calculate the wage amount and the payee detail muster roll is considered as input.
A success toast message is displayed on the creation of the bill.
To view the bill details bill is searched and then view.
Not applicable.
Not applicable.
Not applicable.
Not applicable.
No UI is needed.
1
Bill is created with the approval of the muster roll.
2
Bill gets approved on creation.
3
The bill number is generated as per the specified format given.
4
The bill amount is calculated as per the logic defined in the story.
Bills are created for the work which is in progress and then send for approval process. The approval process contains various workflow levels and states associated with those levels.
Bill is prepared for any work by the Bill Creator (CBO/ JE) and then sent for its verification and approval by the users (actors) in the workflow.
Wage Bill - Approved on create.
Purchase Bill - Sent for verification on create.
Supervision Bill - Approve on create.
1
BILL CREATOR
Create
Search
View
Edit
Submit/ Re-submit
Junior Engineer
2
BILL VERIFIER
Search
View
Edit
Verify and Forward
Send Back
Municipal Engineer
3
BILL APPROVER
Search
View
Approve
Send Back
Send Back To Originator
Reject
Executive Officer/ Municipal Commissioner
1
Submit
Bill Creator
Pending for verification
Submitted
2
Verify and Forward
Bill Verifier
Pending for verification
Pending for approval
Verified
3
Send Back
Bill Verifier
Pending for verification
Pending for correction
Sent Back
4
Send Back
Bill Approver
Pending for approval
Pending for verification
Send Back
5
Send Back To Originator
<roles having access>
<Current Status>
Pending for correction
Sent Back
6
Re-submit
Bill Creator
Pending for correction
Pending for verification
Re-submitted
7
Approve
Bill Approver
Pending for approval
Approved
Approved
8
Reject
<roles having access>
<Current Status>
Rejected
Rejected
The workflow UI component is the same as given for estimate. The only difference is the status update that is displayed as per the details given in the above table.
1
Actions are configured based on role-action mapping.
2
Workflow states are defined as provided and the state transition is done accordingly.
Provide users with the option to verify and forward the bills in the workflow.
Verify and forward action is provided with a pop-up window to capture the below given details.
Assignee name- Drop-down - Non Mandatory - The next user in the workflow i.e. Verification, hence the employees having the role Bill_Verifier are displayed in drop-down with the name and the designation. E.g. Mahesh K working as ME and having the role of Bill_Verifier will be displayed as ‘Mahesh K - Accountant’.
Comments - Text area - Non-Mandatory - In case any comments to be added.
Attach Supporting Document - Non-Mandatory - Any document to be uploaded as a supporting document.
Verify and Forward - Action Button
Cancel - Action Button
On Verify and Forward -
A pop-up window is closed, a toast success message is displayed and the view bill page is refreshed.
The action menu is loaded according to the role-action mapping of the currently logged-in user.
Bill is forwarded to the next user in the workflow and shown in its inbox.
The workflow state changes accordingly and timelines show the current state of the Bill.
Bill is removed from the currently logged-in user’s inbox.
Bill Verifier
Pending for verification
Pending for approval
Verified
On cancel, the pop-up window is closed and a toast cancel message is displayed on the View Bill page.
Toast Success Message: Bill has been forwarded successfully.
Failure Message: Verification of bill failed.
Toast Cancel Message: Action has been cancelled.
Not applicable.
This is a common UI which we have for the verify and forward workflow action.
1
On verify and forward action, the bill is forwarded to the next user in the flow.
2
The pop-up window is closed and the bill page is refreshed. The toast success message is displayed.
3
Workflow states changes and based on the role the existing user has view bill page refreshes.
4
On cancel, the pop-up window gets closed. A toast cancel message is displayed.
Provides users with the option to edit purchase bills.
On submit - A workflow pop-up window is displayed based on the logged-in user role. Users can select the respective workflow action. Any changes are saved and an estimate is forwarded to the subsequent user in the workflow.
On Cancel - the pop-up window gets closed and the action the submit action gets cancelled.
Messages are shown according to workflow stories.
Edit bill action is to be mapped with the Bill Creator.
It is configurable and can to mapped with other roles too on demand.
Only bills in a workflow can be edited. Rejected and Approved bills cannot be edited.
Edit bill allows the user to edit the below-given bill details.
1
Bill number
Read Only
NA
2
Bill date
Read Only
NA
3
Work order number
Read Only
NA
Work Order number
4
Project ID
Read Only
NA
Project ID
5
Project Description
Read Only
NA
Project description of the work.
6
Location
Read Only
NA
Locality + Ward
Invoice Details
5
Vendor's Name
Searchable Drop-down
Y
The organization of type Vendor Only can be searched here by entering at least first 3 chars.
6
Vendor ID
Read Only
Y
Vendor ID of searched and selected vendor is displayed here.
7
Invoice No.
Alphanumeric (64)
Y
Vendor’s invoice number
8
Invoice Date
Date
Y
Invoice date, it can not be a future date.
9
Material Cost
Numeric
Y
10
GST
Numeric
Y
Bill Details
12
Bill Amount
Numeric
Y
Total of Material Cost + GST.
Deductions
Grid
As per the configuration, deductions will be listed, deductions are applicable to vendor’s invoices only.
13
Deduction
Drop-down
NA
Deduction as per the configuration, amount is auto calculated.
14
Percentage/ Fixed
Auto-populated
NA
Deduction as per the configuration, amount is auto calculated.
15
Amount
Auto- calculated
NA
Deduction as per the configuration, amount is auto calculated.
16
Action
Button
NA
Deduction as per the configuration, amount is auto calculated.
17
Total
Auto-calculated
NA
Total of all the deductions added.
18
Net Payable
Read Only
NA
Total bill amount
Relevant Documents
19
Vendor Invoice
File Picker
Y
All the invoices from vendors into one PDF.
20
Measurement Book
File Picker
Y
PDF copy of manual measurement book.
21
Material Utilisation Log
File Picker
Y
PDF copy of material utilization log.
22
Others
Once the estimate is edited, it is re-submitted again for approval process using the action ‘Submit’.
Not applicable.
The user interface for this page is similar to the create bill screen.
1
Role-based access based on configuration.
2
The bill which is in the workflow can only be edited.
3
Bill is opened in editable mode.
4
The details given in the table can be edited by the user.
5
On Submit, the bill is again forwarded to the next user for the approval process.
Create Supervision Bill
Employee
Role: Bill Creator
Bill record gets saved into the system, and the workflow state changes to ‘Approved’.
Bill No. is generated in a specified format.
Format for Work Bill No. is SB-FY-<6digitrunningno.>. Example: SB/2022-23/000051
Bill is available to download in PDF as per the given format. There will be a separate ticket for PDF download.
Supervision bill is created for the supervision of the CBO for in-progress projects.
Supervision Bills are created automatically on approval of the muster roll.
The system should pick only those Wage and Purchase bills which are approved and pending for supervision bill creation.
To calculate the supervision charge amount approved wage bills and purchase bills amount is considered based on the use cases mentioned below.
In case CBO’s role is Implementation Agency
Supervision Charge = (Total of Wage Bills Gross Amount + Total of Purchase Bills Gross Amount) * Supervision Rate/100;
In case CBO’s role is Implementation Partner
Supervision Charge = (Total of Wage Bills Gross Amount) * Supervision Rate/100;
5. To view the bill details, bill search and then view.
Field-level validations as mentioned in the attribute tables.
Not applicable.
Bills get the status approved on creation.
Not applicable.
To CBO - Supervision bill {billnumber} of amount {amount} is approved and forwarded for payment processing.
Create UI is not required.
1
Bill is created with the approval of the muster roll.
2
Bill gets approved on creation.
3
The bill number is generated as per the specified format given.
4
The bill amount is calculated as per the logic defined in the story.
Provide users with the option to edit or submit muster rolls.
Employees.
‘Edit’ Muster roll action is to be mapped with CBO ADMIN and Muster Roll Verifier.
It is configurable and can be mapped with other roles too on demand.
The muster roll which is in a workflow can only be edited.
The approved muster roll cannot be edited.
Edit muster roll allows the user to edit the muster roll.
Only the Days Measured under the attendance details are allowed to edit by Muster Roll Verifier.
Quantity of work (days) values changes according to the change in Days Measured. Quantity of work = Sum of days measured for all the wage seekers.
Once the muster roll is edited, it is re-submitted again for verification/ approval using the action ‘Submit’.
On submit, based on the logged-in user role, a workflow pop-up window is displayed.
CBO ADMIN
Muster Roll Verifier
Verify and Forward pop-up window
On respective workflow action, changes get saved and the muster roll is forwarded to the next user in the workflow.
On Cancel, the pop-up window gets closed and the action gets cancelled.
Accordingly, the messages are shown.
On edit of muster roll, SMS notification is sent to CBO.
Dear <contactpersonname>, Muster roll <musterrollid> for the project <project name> has been modified by the <employeeuser+designation>. Please login to MUKTASoft to see the detail.
1
Role-based access based on configuration.
2
The muster roll which is in a workflow only can be edited.
3
Muster roll is opened in editable mode.
4
The details given in table can be edited by user.
5
On Submit, the muster roll is again forwarded to the next user for the approval process.
Provide users with the option to send back muster rolls to CBO for any corrections or specific action.
Employees.
This feature is provided to send the muster roll back to CBO for any correction required. Below given details are captured.
Comments - Text area - Non-mandatory - It allows users to add any remarks/ instructions to be passed to the originator (CBO) of the muster roll.
Attach Supporting Document - Document upload - Non-mandatory - In case any documents are to be attached while sending the muster roll back to CBO.
Send Back - Action Button
Cancel - Action Button
On Send Back -
The pop-up window is closed and a toast success message is displayed.
The view muster roll page is refreshed and the actions menu is loaded according to the role the logged-in user has.
The muster roll is placed into the muster roll creator/CBO.
The ‘Edit Muster Roll’ option is provided to CBO to edit the muster roll and attached the new documents files and Re-submit it.
Workflow state changes as given below.
<roles having access to send back to originator>
<Current Status>
Pending for correction
Sent Back
3. On cancel, the pop-up window is closed, toast cancel message is displayed on the view muster roll page.
Toast Success Message: Muster roll has been sent back to the CBO successfully.
Failure Message: Sending back of muster roll is failed.
Toast Cancel Message: Action has been cancelled.
Notification is sent to CBO
Dear <contactpersonname>, Muster roll <musterrollID for the project <project name>has been sent back for correction. Please login to MUKTASoft to see the details.
1
The muster roll is moved to CBO.
2
CBO- Edit action is enabled to edit the muster roll.
3
Workflow state changes as mentioned in the ticket.
Provides users with the option to approve muster rolls.
Employees.
For the approval of the muster roll, the Approve action button is provided that captures the below-given details through a popup window on approval.
Comments - Text area - Non-mandatory
Attach Supporting Document - Document upload - Non-mandatory
Approve - Action Button
Cancel - Action Button
On Approve,
The muster roll is approved.
Approve pop-up window is closed, a toast success message is displayed and the view muster roll page is refreshed.
Workflow timelines are displayed accordingly.
Workflow state changes as given below.
Muster Roll Approver
Pending for approval
Approved
Approved
On cancel, a toast cancel message is displayed.
Toast Success Message: Muster roll has been approved successfully.
Failure Message: Approval of muster roll is failed.
Toast Cancel Message: Action has been cancelled.
SMS to the CBO
Dear <contactpersonname>, Muster roll <musterrollID, amount <amount> for the project <project name>has been approved. Please login to MUKTASoft to see the details.
1
On approve - the muster roll workflow state changes accordingly.
2
a SMS notification is sent to the CBO
Provide users with options to verify and forward muster rolls to subsequent workflows.
Employees.
To verify and forward the muster roll to the next workflow user, a pop-up window is provided to capture the below-given details.
Assignee name- Drop-down - Non Mandatory - The next user in the workflow i.e. Approver, hence the employees having the role Muster_Roll_Approver are displayed in drop-down with the name and the designation. E.g. Mahesh K working as ME and have the role of Muster_Roll_Approver will be displayed ‘Mahesh K - Municipal Engineer’.
Comments - Text area - Non-Mandatory - In case any comments to be added.
Attach Supporting Document - Non-Mandatory - Any document to be uploaded as a supporting document.
Verify and Forward - Action Button
Cancel - Action Button
On Verify and Forward -
The pop-up window is closed, a toast success message is displayed and the view muster roll page is refreshed.
The action menu is loaded according to the role-action mapping of the currently logged-in user.
The muster roll is forwarded to the next user in the workflow and shown in its inbox.
The workflow state changes accordingly and timelines show the current state of the muster roll.
The muster roll is removed from the currently logged-in user’s inbox.
Muster Roll Verifier
Pending for verification
Pending for approval
Verified
On cancel, a pop-up window is closed, toast cancel message is displayed on the view muster roll page.
Toast Success Message: The muster roll has been forwarded successfully.
Failure Message: Verification of muster roll failed.
Toast Cancel Message: Action has been cancelled.
Not applicable.
1
On verify and forward, the muster roll is forwarded to the next user in the flow.
2
The pop-up window gets closed and the view muster roll page is refreshed. A toast success message is displayed.
3
Workflow states changes and based on the existing role the user can view the muster roll page on refresh.
4
On cancel pop-up window gets closed. A toast cancel message is displayed.
Provide users with the option to view muster rolls.
Employee
Role: Muster Roll Verifier, Muster Roll Approver.
View Muster Roll
Search Muster Roll→ View Muster Roll
For Muster Rolls in workflow - workflow actions are based on the role of the logged-in user.
Edit
Verify and Forward
Send Back
Send Back To CBO
Approve
For Approved Muster Roll
None (as of now)
To view the details of the muster roll, the View Muster Roll page is provided.
The muster roll is searched using the search Muster Roll feature and then on click of Muster Roll ID, the View Muster Roll page is opened displaying the below details.
Muster Roll ID
Work Order Number
Project ID
Project description
Name of CBO
Role of CBO
Muster roll period
No. of wage seekers
Total attendance (in days)
Quantity of work (in days)
Total wage amount(₹)
Attendance Details - In tabular form
Sr. No.
ID
Name
Father/ Husband Name
Skill
Date/ Day (7 days)
Days Worked
Days Measured
Wage Per Day
Total Wage
Account/ IFSC
Aadhaar (Masked)
Workflow timelines - As per the designed UI.
Not applicable.
Not applicable.
Not applicable.
1
Muster roll details are displayed as described in the story.
2
Actions are enabled as per the muster roll workflow state and role of the logged-in user.
Search a muster roll by various ULB employees/users.
Employee
Role: MUSTER ROLL VERIFIER, MUSTER ROLL APPROVER
Search - To search the result upon supplying the parameter values.
Clear Search - To clear the search parameters supplied.
Search Muster Roll- It has to be configurable and is mapped with a role on demand.
Search Muster Roll is provided to allow the users to search a muster roll and view its details.
1
Ward
Drop-down
Auto-complete, matching search. The values populated from ward boundary master data.
2
Project type
Drop-down
Project type masters value
3
Project name
Textbox
Project name
4
Muster Roll ID
Textbox
Muster roll ID, unique identification no.
5
Status
Drop-down
Workflow state of a muster roll.
6
Created From
Date Picker
Muster roll creation date.
7
Created To
Date Picker
Muster roll creation date.
At least one parameter is required to perform the search.
The date range From Date/ To Date is considered one parameter.
An exact search is performed for the values entered/selected except the project name.
For project name fuzzy search to be enabled.
In case multiple parameter values are supplied AND are applied for searching record.
The search result is shown as given below.
1
Muster Roll ID
Display Only
A hyperlink to open the muster roll in view mode.
2
Project name
Display Only
Project name with project description displayed as tool-tip on mouseover
3
Name of CBO
Display Only
Name of the organization to whom Work Order is awarded.
5
Location
Display Only
Locality name along with ward name. (Locality + Ward)
6
Status
Display Only
Workflow status of the muster roll.
7
Wage Amount
Display Only
Total muster roll amount.
At least one parameter is required to perform the search.
Not applicable.
1
At least one parameter is required to perform the search.
2
Search result displayed on matching records found else no record found message is displayed.
3
Pagination is applied if more than 10 records are found.
Provide users with the option to send back muster rolls to the previous user in the workflow for specific actions.
Employees.
To send the muster roll back to the previous user in the workflow, Send Back action is provided with the below details to be captured.
Comments - Text area - Non-mandatory - It allows users to add any remarks/instructions to be passed on to the previous user in the workflow.
Attach Supporting Document - Document upload - Non-mandatory - In case any documents are to be attached.
Send Back - Action Button
Cancel - Action Button
On Send Back -
The pop-up window is closed and a toast success message is displayed.
The view muster roll page is refreshed and the action menu is loaded according to the role the logged-in user has.
The muster roll is sent back to the previous user inbox.
Workflow states change as per the flow.
Muster Roll Approver
Pending for approval
Pending for verification
Sent Back
On cancel, the toast cancel message is displayed on top of the view muster roll page.
Toast Success Message: Muster roll has been sent back successfully.
Failure Message: Sending back of muster roll is failed.
Toast Cancel Message: Action has been cancelled.
Not applicable.
1
On send back, the pop-up window is closed, a toast success message is displayed and the view muster roll page is refreshed.
2
The muster roll is sent back to just the previous user in the workflow and the workflow timeline gets updated.
3
Workflow state changes based on the role as mentioned in the story above.
4
On cancel, the pop-up window is closed, toast cancel message is displayed.
Provides users with the scope to create purchase bills.
Employee
Role: Bill Creator
Create Purchase Bill
Search Work Order → View Work Order → Create Purchase Bill
On submit - the Forward pop-up window is opened to forward the bill for verification.
On Forward -
Bill record gets saved into the system as bill type Purchase Bill, and attain a workflow state ‘Pending for verification’.
Bill No. is generated in a specified format, if it is direct submit.
Format for bill No. is PB/FY/<6digitrunningno.>. Example: PB/2022-23/000051
The work bill is available to download in PDF as per the given format. There will be a separate ticket for PDF download.
Purchase bill is created for the material supplied for the in-progress projects.
Create Purchase Bill form is developed as per the UI design provided and the attributes listed below.
1
Work order number
Read Only
NA
Work Order number
2
Project ID
Read Only
NA
Project ID
3
Project Description
Read Only
NA
Project description of the work.
4
Location
Read Only
NA
Locality + Ward
Invoice Details
5
Vendor's Name
Searchable Drop-down
Y
The organization of type Vendor Only can be searched here by entering at least first 3 chars.
6
Vendor ID
Read Only
Y
Vendor ID of searched and selected vendor is displayed here.
7
Invoice No.
Alphanumeric (64)
Y
Vendor’s invoice number
8
Invoice Date
Date
Y
Invoice date, it can not be a future date.
9
Material Cost
Numeric
Y
10
GST
Numeric
N
Bill Details
11
Bill Date
Date
Y
Today’s date, display only.
12
Bill Amount
Auto-calculated
Y
Total of Material Cost + GST.
Deductions
Grid
As per the configuration, deductions will be listed, deductions are applicable to vendor’s invoices only.
13
Deduction
Drop-down
NA
Deduction as per the configuration, amount is auto calculated.
14
Percentage/ Fixed
Auto-populated
NA
Deduction as per the configuration, amount is auto calculated.
15
Amount
Auto- calculated
NA
Deduction as per the configuration, amount is auto calculated.
16
Action
Button
NA
Deduction as per the configuration, amount is auto calculated.
17
Total
Auto-calculated
NA
Total of all the deductions added.
18
Net Payable
Read Only
NA
Total bill amount
Relevant Documents
19
Vendor Invoice
File Picker
Y
All the invoices from vendors into one PDF.
20
Measurement Book
File Picker
Y
PDF copy of manual measurement book.
21
Material Utilisation Log
File Picker
Y
PDF copy of material utilization log.
22
Others
Field-level validations as mentioned in the attribute tables.
It is configurable at the ULB level, the stories for configuring the workflow are given separately.
Not applicable.
1
Bill created and attain the status of pending verification.
2
Bill number is generated as per the format given.
Inbox for Employees.
Employees
Menu Links and Search, Filter Apply and Numbers Hyperlinks.
The inbox page for employees to be developed duly taking care of the MUKTA branding aspect.
The inbox of employees is divided into 4 sections.
Menu Title
Product Name
Menu Links
Create Bill - It will redirect users to the Search Work Order page.
Search Bill - It will redirect users to the Search Bill page.
Search Parameters
Bill Number
Project ID
Bill type
Filters
Assigned to me - It will display the work orders in the inbox which are assigned to logged-in users.
Assigned to all - Selected by default, It will display the work orders in the inbox which are pending for action of role(s) logged in user have.
Ward - Multi-select
Locality - Multi-select
Workflow state - state of the workflow of the work order.
Result Display Area
Bill Number
Project Name
Organization Name
Assignee
Workflow State
Amount
SLA days remaining
It should be a DIGIT standard Inbox to allow configuration based on requests from the implementation.
Not applicable
Not applicable
Not applicable.
1
It should be a service-wise inbox for all the employee users.
2
Following the DIGIT standard inbox design.