<Tasks>
1. Inspection Point, 2. Inspection Date, 3. Operation of Inspection Report, 4. Repair Date, 5. Operation of Repair Report, 6.Confirmation
[Maintenance Duty-Without Re-examine: "2. Inspection Date" screen]
<Items>
- Title<<Point>>
- 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)
By the way, there are some people who reacts strongly against "Flowchart". When you show business flowchart to one of those flowchart allergy patient, you'd better give those words, "I made a picture of how inspection goes. I'll explain on it fine and easy." It focused on let him say "Ah, it's easy than I expected!"
Now, Workflow below enables office workers who settled Inspection Point, to order re-examine after inspection has Reported.
<Tasks>
1. Inspection Point, 2. Inspection Date, 3. Operation of Inspection Report, 4. Repair Date, 4b. Confirmation on Inspection 5. Operation of Repair Report, 6.Confirmation on Repair
<Items>
- Title<<Point>>
- inspection Point on GoogleMap(string)
- Ideal Inspection On (date)
- Summary of Inspection(string: text box 3 lines)
- Judgment on Re-examine (select:Need Re-examine/No need Re-examine )
- 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)