- Supplier Upload Data Suppliers initially upload raw data from country/city information to the interface in Figure 15, chapter 5, which requires verification via the system. This raw data is added to the source of the GRIP application, preparing it for processing.
- Data Mapping The system converts the raw driver data into a consistent data schema format and modeling, which is detail on chapter 4.3, making it easier to compare and analyze geographic information from various traffic supplier’ resource.
- Extract Data The extraction phase extracts rules from the YARD Database already in the system. It then compares this with the raw driver data from Suppliers/Customers, looking at various mapping rules such as street name, address, and location rule comparisons.
- Quality Checks The combined dataset is analyzed to identify potential violations of traffic rules or any discrepancies in the data. This part, called Quality Checks, compares traffic regulation rules with driver data.
- Evaluation Check The processed data is cross-referenced with each country's traffic rules to check whether drivers adhere to the regulations. Testing determines whether the data quality is of a good standard.
- Send a report of data qualitypg. 23 Any instances where drivers are not following traffic rules, such as exceeding speed limits or violating size and weight restrictions, are highlighted documents to provide the supplier with a as report.
- Delivery Data The final cleaned data is delivered to the Map Data Product Data Location, referred to as the Quality Table, then prepared and restructured for customer/supplier use.
- Send Clean Data to Customers The cleaned and processed data is then sent to customers for their utilization.
- Saving Backup Data Results The findings and suggested improvements from the final cleaned data after processing are shared and saved to the GRIP Database. This step preserves the data output for any changes in daily updates or monthly processing related to traffic rules.