Data Store
7.3 Violations Data


Description of content

This Data Store shall be used within the Provide Support for Law Enforcement Area. It shall contain details of all the frauds (violations) that have been detected and reported by other functionality.  These include failure by the user to provide the correct payment that is required for the service, violations of traffic rules  (e.g. speed, lane use, red-light or car park) and breaching of an access control system.  Data about the resulting prosecution is also stored.

The data in the Store shall be structured in the following way:
- date of fraud detection (date string)
- date of message to enforcement bodies (date string)
- location of fraud ()
- user ID (number)
- service ID (number)
- type of violation: fraud (characters)
- if financial fraud:
    - nature (characters)
    - account ID (number)
    - amount of overdraft (number - in currency)
- if access control:
    - ID of these systems (number)
    - result (user blocked / user passing through)
- if other:
    - image of violation (video image)
    - involved user ID (number)
    - involved vehicle ID (number)
    - data according to the type of violation (number and/or characters)
- prosecution:
    - date (date string)
    - offence (characters)
    - prosecution decision (number or character indicating YES or NO)

The data must be stored in such a way that the privacy if the user (offender) is maintained according to the rules set out by the European Directives and national laws concerning data privacy.

Diagrams

The Diagram(s) below is (are) the Diagram(s) where you can find the Datastore

Input dataflows

Output dataflows