Tradeflow Violations

Tradeflow violations help in identifying and addressing inconsistencies in shipment processes, ensuring streamlined logistics and operational accuracy.

Functions and types of Data Anomaly

Tradeflow violations represent errors or anomalies in shipment data, categorized into five key types:

Freshness Violations:
These occur when milestone updates, such as an Estimated Time of Arrival (ETA), are outdated. For example, if an ETA has not been refreshed for several days, it triggers a freshness violation, indicating a lack of updated shipment tracking.

Missed Milestones:
This violation type highlights checkpoints skipped during the shipment process. Essential milestones like the Place of Destination (POD) or transshipment locations, if ignored, result in this violation. Missed milestones often disrupt the logical progression of a shipment's journey.

Chronological Order Anomalies:
This type identifies milestones that are not in logical sequence. For example, if a delivery is marked as completed before the departure milestone, it is flagged as an anomaly.

Container and Shipment Inconsistencies:
These violations occur due to errors in shipment details, such as containers listed without transport plans or containers associated with the wrong shipment. For instance, a container might show departure from a different vessel than originally planned.

API Input Errors:
These errors arise when incorrect or incomplete data is submitted via the API. For example, missing or invalid milestone dates, like a departure milestone missing an ETA, are flagged as API input violations.

Each violation type ensures comprehensive monitoring, helping identify errors promptly and improving the shipment management process.

Here is a table summarizing the five types of tradeflow violations:

Violation Type	Description	Example
Freshness Violations	Occurs when milestone updates (such as Estimated Time of Arrival or ETAs) are not updated in a timely manner, indicating outdated shipment tracking data.	An ETA for a shipment has not been updated for several days, indicating the shipment data is not current.
Missed Milestones	Flags checkpoints or milestones that are skipped or overlooked in the shipment process.	A transshipment location is missed, or the Place of Destination (POD) is not recorded.
Chronological Order Anomalies	Identifies situations where the milestones do not follow a logical time sequence.	A delivery is recorded before the departure milestone, indicating the timeline is out of order.
Container and Shipment Inconsistencies	Represents errors in shipment or container data, such as containers listed without transport plans or mismatched shipment details.	A container is listed as part of a shipment but has no associated transport plan or has a mismatched departure.
API Input Errors	Arises from incorrect or incomplete data input via the API, such as missing or invalid milestone details.	Missing Estimated Time of Arrival (ETA) or incorrect dates for departure milestones.

This table clearly outlines the key types of violations and provides practical examples to facilitate understanding and identification within the system.

Technical Side: Where to Find It

The system offers an intuitive dashboard for tracking tradeflow violations, ensuring seamless navigation and management. Here's how the technical aspects align with the functionality:

Dashboard Integration:
Violations are displayed in a dedicated section within the dashboard. The user interface segregates violations by type, providing quick insights into each error. The design ensures visibility is restricted to relevant entities, so users only see violations concerning their organization.

Google Sheets for Review:
Violations are recorded in integrated Google Sheets for detailed analysis. The sheet includes columns for trade codes, violation types, and specific metrics such as the percentage of missed milestones or containers without transport plans. This structured format simplifies identifying, tracking, and resolving issues.

Dynamic Violation Detection:
The system automatically detects and logs violations in real-time. For example, if a container's tracking data lacks an associated transport plan, the violation is immediately flagged and logged under container inconsistencies.

User-Specific Access:
To maintain privacy and relevance, users can only access tradeflow violations related to their entity. For instance, if a violation is created under "ABC," it remains invisible to other organizations like "XYZ"

Toggle Button for Visibility:
Users can enable or disable the display of violations in their settings. A checkbox option in the "Organizations" tab controls whether the violation details are visible in the left-side menu.

Steps to Enable the Tradeflow Violations Button:

Go to Settings:
- Open the Settings menu.
Select the Organization Tab:
- Click on the Organization tab in Settings.
Enable Tradeflow Violations:
- In the Live Data section, check the box for 'Show Tradeflow Violations Button'.
Find the Tradeflow Violations Tab:
- It will appear in the lower-left corner of the interface.

Tabs in Tradeflow Violations:

Freshness TFV: Flags outdated data.
Missed Milestones TFV: Tracks missed milestones.
Data Anomalies TFV: Identifies irregular data.

This document ensures clarity for both functional and technical teams, providing a comprehensive understanding of tradeflow violations and their management within the system. If further technical details or clarifications are needed, the support team can provide additional guidance.