Request Analysis Module
To access, simply go to the main menu and look for the "Business Intelligence" module.
Clicking on it will display all associated submodules, and you must click on "Work Request Analysis" to finally open the window with the corresponding section.
In this module, you will be able to analyze and have full traceability of the work requests that have been reported and managed on the platform.
Dashboard
It presents a complete summary of work request management. It includes a comparison between reported and resolved requests, the total number of requests, resolved and unresolved, average response times, distribution of requests by status, and an analysis of received ratings. This dashboard provides a clear view of performance and efficiency in request management.
Created vs. Finished Work Request
A bar chart comparing created versus finished requests, accompanied by a trend line that highlights the evolution of each data set over time.
- Number of Created Requests: Represents the total number of maintenance requests generated within a specific period.
- Number of Solved Requests: Indicates the total number of maintenance requests that have been successfully completed.
Resolved Requests = Resolved without WO + Resolved with WO + Rejected + Canceled
- Number of Pendings Requests: Shows the number of requests that still require attention or resolution.
Unresolved Requests = Open + In Progress + WO In Progress + Waiting for Another WO + Waiting for a WO + WO Under Review + Request Removed from Pending Tasks
Note: The full details of the information are available in the "Work Requests" module.
Work Requests by Status
A horizontal bar chart displaying the distribution of all requests over a given period, classified according to their status. This chart allows users to clearly visualize the number of requests in each status, facilitating management analysis and progress tracking.
Average Response Times
- Average Time for First Response: Reflects the average time elapsed from request creation to the first interaction or response from the maintenance team. This time is crucial as it directly impacts the commitment to providing quick responses.
- Average Timout Solution: Represents the average time users must wait from request creation until its complete resolution by the maintenance team.
- Average Time Of Solution: Indicates the average duration required to resolve a request from the moment it is created. This metric affects operational efficiency and internal customer satisfaction.
Note: This information panel details the data sources, ensuring transparency and guaranteeing the understanding and reliability of the information.
Request Ratings and Averages
- Work Request Rating Percent: Displays the percentage of requests that have been evaluated or rated by users after resolution. A high rating rate may indicate good internal customer satisfaction.
- Rating Average: Represents the average score given by users to the solutions provided by the maintenance team. It serves as a key indicator of service quality.
Within the dashboard, users can download charts in SVG, PNG, and CSV formats, providing flexibility and ease in managing visual information.
- The SVG format allows for scalability without loss of quality, making it ideal for adapting to different platforms and screen sizes.
- The PNG format ensures high-quality images with transparency, making it perfect for sharing charts clearly.
- The CSV format makes underlying chart data easily available in a tabular format, allowing for detailed analysis and efficient collaboration.
These options enhance the user experience, promote collaboration, and ensure the effective dissemination of information to support informed decision-making.
Rating
The "Rating" is a system designed to evaluate and assign a score to the individual performance of a responsible person, whether an employee, team leader, or any other individual in charge of managing work requests recorded on the platform.
Assets in Work Request
In this tab, users can quickly view a list of assets that have had work requests, as well as a count of the number of requests for each of these assets. This type of analysis is extremely important, as it allows for identifying which assets have had the highest number of incidents that resulted in unplanned work requests.