It's not a simple story. Maintenance costs rise up if all the detection of sensors had inspected right at the time. It may affect Corporate cost structure. But you cant leave it.
So make "Conditions" if response immediately or not. In this kind of workflow, the most improving point may be to brush up imposing conditions.
similar article;
- "Maintenance Duty Certainly Is A Flow"
- "Periodic Or Emergency, Maintenance Duty Goes On Almost the Same Flow"
<Tasks>
1. Inspection Point, 2. Inspection Date, 3. Operation of Inspection Report, 4. Repair Date, 5. Operation of Repair Report, 6.Confirmation
[Maintenance Duty-Receive Inspection Data:[2. Inspection Date] screen]
<Items>
- Title<<Point>>
- Temperature (numeric)
- Alternative machine working (numeric)
- inspection Point on GoogleMap (string)
- Ideal Inspection On (date)
- Summary of Inspection(string: text box 3 lines)
- Correspondence (discussion)
- Schedule Inspection On (date)
- Inspected On (date)
- Photo Inspecting (file)
- Inspection Report (string: text box 3 lines)
- Judgment (select:Need to be Repaired/No Need to be Repaired)
- Schedule Repair On (date)
- Repaired On (date)
- Photo Repairing (file)
- Repair Report (string: text box 3 lines)
Please imagine emergency maintenance on vending machines or elevators. In the Workflow above, a case with [Temperature (numeric)] and [Alternative machine working (numeric)] have added are supposed. It automatically decides where to start by those numbers, either
- from Office worker's Task [1. Inspection Point] or
- from Inspector's Task [2. Inspection Date]
And workflow model with "Emergency alert will sent by email depends on information from sensors" would be also better for the inspector to quick catch from sensors.
<Tasks>
1. Inspection Point, 2. Inspection Date, 3. Operation of Inspection Report, 4. Repair Date, 5. Operation of Repair Report, 6.Confirmation
<Added Items>
None