Work order is created for an approved estimate in order to award the work to CBO. CBO starts the work to complete it within a given time period.

In case organization comes to know that they are not in a position to complete the work within the given time frame due to various reasons, they need to inform the same to the officer in-charge of project and apply for time extension which is then subject to approval/ canceling of work order based on the analysis done by the ULB.

Requests for time extension can be directly raised by CBO using the mobile application and by the officer in-charge of the project on behalf of CBO using web application. Once a request is raised it goes for verification and approval.

We have the following screens for Time Extension in Web Interface

• Create Time Extension

• View Time Extension

• Edit Time Extension

• Search Time Extension ( Same as search work order screen)

• Inbox ( Same as work order inbox )

Conditions to Create a Time Extension Request

• Work order must be in Accepted state

• Existing Time Extension requests, if already created, must not be in workflow

• At Least one muster roll must be approved

How to Create a Time Extension Request in Web-Interface

• Login with work order creator role and Navigate to Home page.

• Home > Work Orders > Inbox > Search Work Order > View Work Order > Request Time Extension (From Action Menu)

• A screen similar to the Work Order View screen is opened along with two new input fields

• Enter time extension value (in days) and reason in those two inputs and click on Create action button

• A workflow popup is opened where users can enter the assignee and relevant comments. Click on Submit button

• A response page is opened which shows the newly created revised work order application’s number

Inbox, View and Search Screen For Time Extension in Web Interface

There is no separate inbox for time extension. Work order inbox will list the time extension requests which are INWORKFLOW state. Clicking on the time extension request will open a view time extension screen where the user can take actions on the request based on the roles defined in the workflow. Alternatively, users can go to the work order search screen to search for any time extension request.

Workflow for Time Extension

Overview

This module helps in creating a work order for the Project based on the estimates designed. This enables in deciding the Tendering, Quotation and Nomination. Based on the nomination, CBO is being mapped to the respective work order.

This module has 5 associated screens :

1. Create

2. Search

3. Modify

4. View

5. Inbox

MDMS Configurations

Module Enablement Configuration

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

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

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

Role-action Mapping

Sidebar Configuration

{
      "id": 58,
      "name": "CONTRACTS",
      "url": "url",
      "displayName": "Contracts Inbox",
      "orderNumber": 2,
      "parentModule": "",
      "enabled": true,
      "serviceCode": "CONTRACTS",
      "code": "null",
      "navigationURL": "/works-ui/employee/contracts/inbox",
      "path": "3CONTRACTS.Inbox",
      "leftIcon": "dynamic:ContractIcon"
   }

Screen Configuration

Localization Configuration & Modules

Workflow Configuration

Customization

1. API-based Data -

• Name of CBO - This field is being captured on the Create screen and Modify screen. Data for this field comes from the backend.

• CBO ID - This field is being set based on the value selected in the Name Of CBO.

• Name of Officer In Charge - This field is being populated based on the HRMS Search. Here the role is hardcoded to ‘OFFICER_IN_CHARGE’.

• Designation of Officer In Charge - This field is being set based on the value selected in the Name of Officer in charge.

• Work Order Amount - This field shows the calculated amount of Total Estimated Cost minus the Overheads which has ‘isWorkOrderValue’ as true. Please refer to this OverHeads config for Amount calculation.

• The role of CBO will be shown based on the calculated Work Order Amount. If the calculated Work Order Amount is less than the ‘amount’ in RoleOfCBO Config, show Implementation Agency else show Implementation Partner. This logic will vary based on the updates in the RoleOfCBO config.

2. Custom Components used in Projects :

• Document Config - Based on the document config, respective documents will be rendered on the Create Screen. Please mention the validations, file type limits and file size limits in this config.

• Work Order Terms and Conditions - This component will help input the description in the table. Users can add and delete the rows. The first row will not be deleted, clicking on the delete button will empty the first row. Refer Component - WOTermsAndConditions.

3. Create Screen:

• Please use the common Utility “PreProcessMDMSConfig”.

• Pass the associated dependencies for the config.

• The utility will return a config which will run through FormComposer.

• Refer to docs for Pre-Process config in Component comments.

4. Inbox / Search Screen :

• Please use the common utility “preProcessMDMSConfigInboxSearch”.

• Pass the associated dependencies for the config.

• The utility will return a config which will run through RenderFormFields.

• Refer to docs for Pre-Process config in Component comments.