Overview

This Function shall be capable of providing the following facilities:

(1) The ability to carry out the classification of the fraud notifications received from the functionality in other Areas or directly from the Detect Fraud Function.
(2) If the violator's identity is not included in the notification, the ability to send the data that is available to the Identify Violator Function for it to be retrieved.
(3) The ability to carry out the classification according to different criteria: level of seriousness, field (road, financial, commercial...) and repeat offence.
(4) Once the classification has been completed, the ability to send it together with all the other information about the violation to the Establish Prosecution File Function.

Functional Requirements

(a) continuously monitor for the receipt of any fraud (violation) notification sent by the other functionality
(b) when any of the data flows in (a) is received, process it and extract the violator ID
(b) if the violator ID is not in the notification received in (b), extract any elements useful for this identification, and send them to the Identify Violator Function, using the first other output data flow
(c) await receipt of the data resulting from (b) which will arrive in the fifth trigger input data flow
(d) note that the data flow in (c) will be accompanied by the fourth other input data flow
(e) extract from the store of Violations Data the seriousness of the fraud, receiving the data in the third other input data flow
(f) also search in the store of Violations Data to see if the violator has already committed other similar offences before, receiving the data in the second other input data flow
(g) dispatch the notifications according to the format of the fraud in the first trigger output data flow to the Establish Prosecution File Function
(h) send all the data about the fraud (violation) to the Fraud Function, using the second trigger output data flow
(i) where the driver and/or vehicle ID is known, send the data to the Manage Traffic Area, using the appropriate of the first and second trigger output data flows, depending on whether the fraud (violation) was committed in the inter-urban or urban road network.

Diagrams

Parent Higher Level Function

• 7.3 Process Fraud and Violation Notifications

Input logical dataflows

• mffo.psle_violation_notification
• mt.psle_illegal_carpark_space_occupancy
• mt.psle_inter-urban_vehicle_identity_error
• mt.psle_inter-urban_violating_vehicle_identity
• mt.psle_urban_vehicle_identity_error
• mt.psle_urban_violating_vehicle_identity
• mt.psle_vehicle_entering_inter-urban_zone
• mt.psle_vehicle_entering_urban_zone
• pepf.psle_fraud_notification_DAV
• pepf.psle_fraud_notification_DPV
• pscs.psle_bus_lane_violation
• psle_classification_of_fraud_or_violation
• psle_violation_history_for_notification
• psle_violation_seriousness
• psle_violation_type_from_compliance_check
• psle_violation_type_from_image_analysis
• psle_violation_type_from_violator_determination
• psle_violator_ID
• psle_violator_ID_from_violator_determination

Output logical dataflows

• psle_fraud_characteristics
• psle_inter-urban_violator_ID
• psle_urban_violator_ID
• psle_violation_notification_for_storage
• psle_violator_data_for_image_analysis

User needs