Case Control OK (valid right)
If the result of the control has a valid right, the agent can either:
●proceed to control the next vehicle.
●Invalidate the control (see PATCH /controls request example in the appendix) and establish a Fine when they estimate that the right does not match the visual inspection of the vehicle. E.g., a valid e-ticket for electric vehicle while the vehicle is visually found non-electric, or a bad area detected by the PDA.
In this second case, the control service will store two controls:
1.The first control with a status "reprocessed", and a link pointing to the 2nd control.
2.The second control with a status "KO"
After establishing the Fine, the PDA will update the control to "ControlStatusFined", provide a link to the created Fine, and provide the reason for the Fine (fineReason as specified in the appendix).
Step 2: Control result processing (Control Ok)
Case control KO (no valid rights)
The Agent has three options:
1.Tolerate the parking of the vehicle (example: ticket expired for a very short time), in this case the agent specifies that the parking of the vehicle is tolerated and specifies the reason for this tolerance (selection in a predefined list).
The application will then store a control with the status "OK" and the reason of the tolerance indicated by the agent (toleranceReason as specified in the appendix)
Step 2: Control result processing (Control KO - tolerance)
Exempt the vehicle following a visual inspection (example: person of reduced mobility), in this case the agent specifies that the vehicle is exempted and specifies the reason for this exemption (selection in a predefined list).
In this case the application will then store a control with the status "exempted" and the reason for the exemption given by the agent (exemptionReason as specified in the appendix)
Step 2 : Control result processing (Control KO - exemption)
2.Issue a fine. See Issue a fine
