Create Work Order
Context
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.
Scope
Create Work Order
Search Estimate → View Estimate → Create Work Order.
Actors
Employee
Role: Work Order Creator
Details
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.
Attributes
Validations
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.
Configurations
The amount limit deciding the role of CBO should be configurable. At present it is 15 lakh.
Workflow
The stories for configuring the workflow are given separately.
Actions
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.
Notifications
Not applicable.
User Interface
Acceptance Criteria
Last updated