In Consumer Evolution, a work request allows you to register and manage service requests related to company assets.
It is mainly used to report a need or problem that will subsequently need to be assessed and managed, and may result in maintenance tasks, a work order, or a resolution without a work order.
Information from an application
Each request includes information that allows the requirement to be identified and managed.
Its main features include:
Qualification
It allows you to register a brief description of the requirement to facilitate its identification.
Asset
It allows you to specify the affected asset.
The request can be created without selecting an asset if the asset has not yet been identified or is not registered. To proceed with the maintenance planning later, the corresponding asset must be specified.
The fields available in an application can be configured as visible, optional, or mandatory depending on the company's needs.
Status of an application
During its processing, an application can go through different stages:
- Open: The application has been created and some of the data necessary to proceed with its processing is not yet complete.
- In process: The request has begun processing. It can reach this status by adding tasks or by manually marking it as In process .
- Work order in process: The request has associated tasks and a work order was generated for its execution.
- Resolved: The request was resolved without the need to manage it through a work order.
- Unauthorized: The request was not authorized and therefore will not proceed with the generation of a work order or its resolution. Authorization is configured through request categories.
| State | Observations |
|---|---|
| π£ Open | The application has been created, but some of the data needed to proceed with its processing is not yet complete. |
| π‘ In progress | The request has begun processing. It can reach this status by adding tasks or by manually marking it as " In Process" . |
| π’ OT in progress | The request has associated tasks and a work order was generated for its execution. |
| π΅ Resolved | The request was resolved without the need to manage it through a work order. |
| βͺ Not authorized | The request was not authorized and, therefore, the generation of a work order or its resolution will not proceed. Authorization is configured through request categories. |
Application categories
The categories allow you to define different management criteria for requests, such as available fields, active fields, urgency levels, work teams, tasks, responsible parties, authorizations, and compliance.
Its configuration is done from Settings > Request Categories .
[IMAGE: Job application showing title, active, category and status]