Output Data Requirements Sample Clauses

Output Data Requirements. 2.2.1 Each Detection Event that matches a VRM on the VOSI List will result in a copy of the Detection Event being sent to the VOSI System. 2.2.2 The copy of the Detection Event must be sent immediately to the VOSI System. 2.2.3 Regardless of whether a Detection Event is identified as being on the VOSI List, the Detection Event needs to continue through Event Processing.

Output Data Requirements. 3.2.1 Each Detection Event will need to be updated with the Scheme that it is associated with.

Output Data Requirements. 4.2.1 Any Detection Event that is captured within the date and time range by the Camera ID and Scheme will be discarded.

Output Data Requirements. 5.2.1 Each Chargeable Item matched against the Exempt Vehicle List will need to be assigned the relevant Exempt Product Identifier. 5.2.2 The Product Identifier should be different for each type of exemption.

Output Data Requirements. 6.2.1 Each Chargeable Item matched against the Black List or not matched against the White List, will need to be assigned the relevant Product Identifier. 6.2.2 Any Chargeable Item that is not matched against the Black List, or is matched against the White List, is discarded and assigned the relevant Product Identifier.

Output Data Requirements. 7.2.1 Each Chargeable Item matched against the Compliant List will need to be assigned the relevant Compliant Product Identifier. 7.2.2 The Compliant Product Identifier should be different for each type of Compliance.

Output Data Requirements. 8.2.1 Each Chargeable Item matched against the Discount Vehicle List will need to be assigned the relevant Discount Product Identifier. 8.2.2 The Discount Product Identifier should be different for each type of discount.

Output Data Requirements. 9.2.1 Each Chargeable Item matched against the TfL Filter Vehicle List will need to be assigned the relevant TfL Filter Product Identifier.

Output Data Requirements. 10.3.1 Each Chargeable Item matched against the Settlement List will need to be assigned the relevant Payment Product Identifier. 10.3.2 Where the Chargeable Item has a Discount Product Identifier associated with it, the Payment Product should be verified.

Output Data Requirements. 11.2.1 Each Chargeable Item matched as a Contravention Candidate Product must be sent to the Enforcement Operations Notice Processing Service Provider. 11.2.2 Reporting on volumes of Chargeable Items identified as Contravention Candidates must be available by Camera ID, Scheme and date of capture.