Maintenance Accident Report Process 20230221<\/div>
This is the process for reporting work problems for field engineers. The problem report will be submitted in a public form. The accepted engineer ID is used to determine whether the engineer is legitimate or not. At the same time, attributes such as email address and phone number are obtained.<\/div><\/div>\n\n\n
<\/span>Workers (Number of swimlanes: 2)<\/div>
\n\n\n\n
- \n
- <\/i><\/span><\/span> Field Engineer<\/strong> <\/li>\n\n\n\n
- <\/i><\/span><\/span> Troubleshooting Headquarters<\/strong> <\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
<\/span>Workflow (Complexity of workflow diagram: 20)<\/div>\n\n\n\n- \n
- Response instruction<\/strong>\n
- \n
- The staff at the troubleshooting headquarters will describe the response instructions.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x1. Get Engineer Profile<\/strong>\n
- \n
- The workflow platform retrieves the registration information for the corresponding ID from the engineer master.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span><\/span>x10. Historical addition<\/strong>\n
- \n
- The workflow platform stores problem reports in the history.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x2. Engineer Name<\/strong>\n
- \n
- The workflow platform extracts the name from the engineer’s information.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x3. Engineer Kana Name<\/strong>\n
- \n
- The workflow platform extracts the name (kana) from the engineer’s information.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>31<\/span><\/span><\/span>x4. Engineer E-Mail<\/strong>\n
- \n
- The workflow platform extracts email addresses from the engineer’s information.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x5. Engineer Tel no<\/strong>\n
- \n
- The workflow platform extracts the phone number from the engineer’s information.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x6. Engineer Location Number<\/strong>\n
- \n
- The workflow platform extracts the location No. from the engineer information.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x7. Subject<\/strong>\n
- \n
- The workflow platform generates a subject line and stores the report in the history.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x8. Historical addition<\/strong>\n
- \n
- The workflow platform stores the instructions in the history.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- x9. Time Stamp<\/strong>\n
- \n
- The workflow platform generates a processing completion timestamp for the problem response reporting process.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- \u25c6 Troubleshooting Report<\/strong>\n
- \n
- The field engineer reviews the instructions and determines the end of the case.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n<\/span>Workflow Diagram (click to open)<\/div>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/support.questetra.com\/wp-content\/uploads\/2023\/02\/maintenace-accident-reception-process-20230221-diagram.png?resize=1024%2C310&ssl=1\")
<\/figure>\n\n\n\n- \n
- BPMN Icons\n
- \n
- Start Event<\/li>\n\n\n\n
- End Event<\/li>\n\n\n\n
- Merge Gateway (XOR)<\/li>\n\n\n\n
- Exclusive Gateway\n(XOR)<\/a><\/li>\n\n\n\n
- Throwing Message Intermediate Event (email)<\/a><\/li>\n\n\n\n
- Human Task<\/a><\/li>\n\n\n\n
- Update Data<\/a><\/li>\n\n\n\n
- String, Decode using Master Table<\/a><\/li>\n\n\n\n
- Singleline CSV String, Extract Cell\n<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
- Throwing Message Intermediate Event (email)<\/a><\/li>\n\n\n\n
- BPMN Icons\n
- The field engineer reviews the instructions and determines the end of the case.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
- <\/i><\/span><\/span> Troubleshooting Headquarters<\/strong> <\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n