All Collections
Requests
Work requests
How to manage and convert a work request into a WO?
How to manage and convert a work request into a WO?
CustomerSuccess Team avatar
Written by CustomerSuccess Team
Updated over a week ago

Once a work request has been generated, the system allows you to manage such request through an non scheduled task to do this, you must click on the add symbol.

Then when you click on it, a new window will be enabled, where you must complete all the information corresponding to the non scheduled task that can be sent to Work Queues (to be scheduled later) or generated as a new work order.

To do this, they must establish 4 steps before managing the task:

  • Assets: Information associated with the asset and its status.

  • Task: Information associated with the non scheduled task.

  • SubTasks: Listing of the subtasks or check-list (step-by-step) that must be accomplished to successfully complete the task.

  • Resources: Resources to be used in the execution and fulfillment of the task.

Step 1:

  • The Asset has failed?: Option where you can indicate if the non scheduled task involves the failure of the asset.

  • Fault Type: Catalog with the types of faults associated with the assets.

  • Fault Cause: Catalog with the causes that can lead to asset failures.

  • Fault detection method: Catalog with the detection methods by which a fault can be identified.

  • Fault Severity: Listing of fault hierarchy options according to severity.

  • Type of damage: List with default options to identify the type of damage caused by the asset failure.

  • It caused disruption of other assets: Time in which the failure directly affects other assets.

  • Assets Out of service: State in which the equipment is stopped due to a functional failure. This field is extremely important, since when it is activated, the date and time from when the equipment was stopped must be entered (this time is the one taken for one of the availability indicators in the Business Intelligence module).

Step 2:

  • Task Description: Short detail specifying the task in question.

  • Note: Free field where you can add some details of the task.

  • Task Type: Catalog with all the types of tasks registered in the system.

  • Group 1 and 2: Corresponds to free fields left by the platform to be completed and give an additional classification to the task.

  • Priority: List where the task is classified according to its priority.

  • Estimated Duration: Theoretical time duration it would take to perform the task (the actual time is recorded directly in the WO).

  • Request Number: Identification correlative of the request that generates the unplanned task.

  • This task has already been done: Option that allows to identify in the system if the task has already been executed or not.

  • Options: Options available to manage the non scheduled task through a WO (the person responsible for the WO must be added) or Work Queues (the date on which the task will be scheduled must be added).

Step 3:

In this step, you must add the associated subtasks, to do this you have to click on the add symbol that is located in the lower right part of the platform and then add the subtasks as appropriate.

Step 4:

In this last step you can add the resources associated to the non scheduled task, where you can add: Inventories, Human Resources, Services, Inventories (Not Cataloged), Services (Not Cataloged).

Then, at the end of the management of the non-scheduled task, you can see the change in the status of the request and the correlative of the generated WO (if this option was chosen to manage the task).

Did this answer your question?