Post by account_disabled on Mar 14, 2024 15:01:30 GMT 5.5
Of any large service company. This is roughly how everything works for us the process of receiving and processing requests for maintenance or repair of equipment is generally standard The customer sends an email or creates a request in Jira we receive a request with the status new. It is picked up by the hour first line and then we look at the serial number is it beating or not is it supported or not we supplement the application with information and transfer it to specialized engineers. An engineer joins. If necessary he carries out additional diagnostics orders spare parts and moves the request further.
From one status to another in progress awaiting delivery etc. When the work is completed the customer receives a notification asking him to evaluate the work. For him this is where the path ends but for us it can continue. Engineers return unused spare Buy Email List parts to the warehouse test the hardware and analyze the causes of the incident. Afterwards we send a request for closure from the engineer. Finally the first line evaluates the engineers work and closes the request completely. Next is the archive we store all information about applications for at least three years. According to data for we had service requests faults involving.
Trequests for maintenance and prevention consulting issues. Thats claims per quarter per month per week an average of claims per day and . per minute. The lions share of them came through the client portal based on Jira Service Desk which we switched to in from HPSM an outdated legacy solution that only works on the desktop and with a problematic update process. Jira has incorporated a lot of processes within the company. All projects are carried out in it engineers are not scattered among services for ordering and sending spare parts and solving requests and clients can monitor all this.
From one status to another in progress awaiting delivery etc. When the work is completed the customer receives a notification asking him to evaluate the work. For him this is where the path ends but for us it can continue. Engineers return unused spare Buy Email List parts to the warehouse test the hardware and analyze the causes of the incident. Afterwards we send a request for closure from the engineer. Finally the first line evaluates the engineers work and closes the request completely. Next is the archive we store all information about applications for at least three years. According to data for we had service requests faults involving.
Trequests for maintenance and prevention consulting issues. Thats claims per quarter per month per week an average of claims per day and . per minute. The lions share of them came through the client portal based on Jira Service Desk which we switched to in from HPSM an outdated legacy solution that only works on the desktop and with a problematic update process. Jira has incorporated a lot of processes within the company. All projects are carried out in it engineers are not scattered among services for ordering and sending spare parts and solving requests and clients can monitor all this.