Your Transportation Management Data Template

The Activity Name describes a discrete step or status update in the transportation process, such as 'Carrier Assigned', 'Goods Picked Up', or 'Shipment Delayed'. These activities form the nodes of the process map, and their sequence defines the shipment's journey.

Analyzing these activities is the core of process mining. By examining the order, frequency, and duration between activities, analysts can identify bottlenecks, rework loops, and inefficient process variants. This attribute is essential for building dashboards that track process flow and calculating KPIs related to specific process steps.

This attribute defines the steps in the transportation process, allowing for the visualization of the process flow and the identification of bottlenecks.

Derived from event type or status update fields within the project44 event tracking data streams.

Event Time is the date and time recorded for each activity in the shipment's lifecycle. This chronological data is the backbone of process mining, as it allows for the reconstruction of the process flow exactly as it happened.

This attribute is used to calculate all duration-based metrics, including cycle times, waiting times, and processing times. It is fundamental for identifying delays, measuring performance against schedules, and understanding the temporal dynamics of the transportation process. All time-related KPIs, such as On-Time Delivery Rate and Average Transit Time, depend on accurate Event Time data.

This mandatory timestamp enables the chronological ordering of activities and is the basis for all performance and duration calculations.

This corresponds to the timestamp associated with each event in the project44 data feed.

The Shipment attribute is the central case identifier that groups all related events and activities for a single transportation order. It allows for a complete, end-to-end analysis of the shipment lifecycle, from its creation and carrier assignment through transit, delivery, and final payment processing.

In process mining, analyzing by Shipment is fundamental. It enables the visualization of process maps, calculation of cycle times for individual shipments, and the identification of common or deviant process paths. All other attributes, such as carrier, delay reason, or cost, are analyzed in the context of this unique identifier.

This is the essential Case ID that connects all related transportation events, making it possible to trace the end-to-end journey of each shipment.

This is the primary key for shipment data within project44, often referred to as Shipment ID or Tracking Number in the platform's API and user interface.

This attribute records the date and time the data was last extracted or updated from project44. It provides crucial metadata about the freshness of the analysis.

Analysts use this information to understand if they are viewing the most current data available. It is essential for operational dashboards that monitor ongoing shipments and for ensuring that any conclusions drawn from the analysis are based on up-to-date information.

Indicates the freshness of the data, ensuring that analyses are based on current information and supporting operational monitoring.

This timestamp is generated and added during the data extraction and loading (ETL) process.

This attribute identifies the source system providing the data, which in this case is 'project44'. In broader scenarios, it could also specify data coming from an integrated TMS, ERP, or carrier system.

Understanding the source system is important for data governance and troubleshooting. It helps in assessing data quality and reliability, especially when data is aggregated from multiple platforms. For this analysis, it confirms that the events are being tracked via the project44 visibility platform.

Identifies the origin of the data, which is crucial for data governance, quality assessment, and understanding the data's context.

This is typically a static value ('project44') added during data ingestion to label the dataset's origin.

This attribute identifies the logistics company or carrier handling the transport of the goods. It could be a trucking company, airline, or ocean liner.

Analyzing performance by carrier is a primary goal of transportation management analysis. This attribute allows for the segmentation of KPIs like On-Time Delivery Rate and Average Transit Time by carrier. It directly supports the 'Carrier Performance and Compliance' dashboard, helping to identify top-performing and underperforming partners.

This is critical for evaluating and comparing carrier performance, enabling data-driven carrier selection and negotiation.

Available within the shipment details in the project44 platform, associated with each shipment.

When a shipment is delayed, this attribute provides the reason, such as 'Weather Conditions', 'Customs Hold', or 'Port Congestion'. This information is captured when a 'Shipment Delayed' event occurs.

This is a key attribute for root cause analysis. It powers the 'Delivery Delay Root Cause Analysis' dashboard by allowing analysts to categorize and quantify the most common sources of delays. By understanding why delays happen, organizations can develop targeted strategies to mitigate risks and improve on-time performance.

Enables root cause analysis of delays, helping to identify the most common problems and focus improvement efforts effectively.

Captured as part of a delay event or status update within the project44 data stream.

This attribute specifies the country where the shipment's journey ends. It is part of the destination location details.

Paired with Origin Country, this attribute is crucial for analyzing transportation lanes. It helps uncover performance differences between domestic and international routes, highlights countries with frequent customs delays, and provides context for variations in transit times and costs. It is essential for dashboards focusing on geographic performance and delay hotspots.

Crucial for analyzing transportation lanes, comparing domestic vs. international performance, and pinpointing cross-border issues.

Part of the destination address information associated with the shipment in project44.

This attribute specifies the transportation mode. A single shipment may involve multiple modes, but this typically refers to the primary mode used for the main leg of the journey.

Segmenting analysis by Mode of Transport is crucial for understanding performance variations. Different modes have distinct process flows, costs, and typical durations. This attribute allows for apples-to-apples comparisons and helps tailor improvement initiatives to the specific challenges of truckload, LTL, air freight, or ocean shipping.

Allows for performance and cost analysis to be segmented by transportation mode, which is essential due to their different operational characteristics.

A standard data point associated with shipment details in project44.

This attribute specifies the country from which the shipment begins its journey. It is part of the origin location details.

Geographic analysis is vital for identifying regional performance issues. By using Origin Country and Destination Country, analysts can create performance maps, identify problematic lanes, and understand how customs or cross-border movements impact cycle times. It directly supports the 'Geographic Shipment Performance Map' dashboard.

Enables geographic analysis of performance, helping to identify region-specific bottlenecks, especially for international shipments.

Part of the origin address information associated with the shipment in project44.

This attribute stores the target delivery date for the shipment. It serves as the baseline against which actual delivery performance is measured.

This date is essential for calculating the 'On-Time Delivery Rate' KPI. It is compared with the timestamp of the 'Goods Delivered' activity to determine if a shipment was on-time, early, or late. This analysis is fundamental to measuring customer satisfaction and supply chain reliability.

This is the benchmark for calculating the On-Time Delivery Rate KPI, a critical measure of service level and customer satisfaction.

Typically part of the initial shipment order data, sourced from a TMS or ERP and visible in project44.

This attribute represents the actual or accrued cost for transporting the goods. This can include freight charges, fuel surcharges, and other accessorial fees.

Cost is a critical dimension for process mining analysis. By linking cost data to process data, organizations can identify which process variants, carriers, or delays are driving up expenses. It directly supports the 'Transportation Cost Overrun Insights' dashboard by allowing analysts to correlate high-cost shipments with specific process inefficiencies.

Integrating cost data with process flow allows for the identification of cost drivers and inefficiencies, enabling true cost-to-serve analysis.

This information may come from an integrated TMS or ERP system, or from freight audit and payment processes linked to project44 data.

This attribute identifies the end customer for the shipment. This information is critical for understanding performance from a customer-centric point of view.

Analyzing performance by customer helps identify if specific customers are experiencing higher delay rates or longer cycle times. It supports the 'On-Time Delivery Performance Trend' dashboard by allowing segmentation by customer, revealing valuable insights for customer relationship management and service improvement.

Allows for customer-centric analysis, helping to identify service level issues and improve satisfaction for key accounts.

This data is typically part of the shipment order information, originating from an ERP or TMS and passed to project44.

While EventTime (StartTime) marks the beginning of an activity, EventEndTime marks its completion. This is particularly relevant for activities that have a duration, such as 'Customs Clearance' or 'At Border Crossing'.

Having both a start and end time allows for the precise calculation of activity processing times. For example, the 'Customs Clearance Duration' KPI is calculated as the difference between the EventEndTime and EventTime for the 'Customs Cleared' activity. This provides much more accurate insights into bottlenecks than just measuring the time between different activities.

Enables the precise calculation of durations for activities that span a period of time, such as customs clearance or dwell time.

For some events, project44 may provide both a start and end timestamp. Otherwise, it might be the timestamp of the next event.

This calculated attribute simplifies performance analysis by providing a clear 'true' or 'false' value for on-time status. It is derived by comparing the timestamp of the 'Goods Delivered' activity against the 'RequestedDeliveryDate'.

In dashboards and reports, this flag allows for easy counting, filtering, and visualization of on-time versus late shipments. It is the basis for calculating the overall 'On-Time Delivery Rate' KPI and can be used to segment performance across various dimensions like carrier, route, or customer.

Provides a simple, binary outcome for delivery performance, which is ideal for calculating KPIs and creating summary dashboards.

This attribute is not in the source system. It is calculated during data transformation by comparing 'EventTime' of the 'Goods Delivered' activity with the 'RequestedDeliveryDate'.

This attribute stores a reference number or link to the Proof of Delivery (POD) document, which confirms the shipment was received. The 'Proof of Delivery Received' activity marks when this document is available.

Tracking the POD is critical for the financial settlement part of the process. This ID helps link the physical delivery to the administrative processes of invoicing and payment. It is used in the 'POD and Payment Processing Times' dashboard to analyze the efficiency of post-delivery operations.

Links the physical shipment to the financial settlement process, enabling analysis of the time taken to receive delivery confirmation for invoicing.

This information is often captured in an event or document management system integrated with project44.

This attribute contains the scheduled timestamp for the final delivery. This is often a more specific appointment time than the overall 'RequestedDeliveryDate'.

This timestamp is crucial for calculating the 'Delivery Schedule Adherence' KPI. It allows for a more granular analysis of final-mile performance by comparing the scheduled appointment with the actual 'Goods Delivered' timestamp. This helps identify issues with delivery appointments and driver punctuality.

Provides the benchmark for the 'Delivery Schedule Adherence' KPI, enabling analysis of final-mile execution and carrier punctuality.

Available in the appointment or scheduling data within project44, often set via the TMS.

This attribute stores the scheduled timestamp for the pickup. It is established during the planning phase, after a carrier is assigned.

This date is used to measure 'Pickup Schedule Adherence'. By comparing the 'ScheduledPickupDate' with the actual timestamp of the 'Goods Picked Up' activity, organizations can assess the reliability of carriers and the efficiency of their own warehouse operations. It helps pinpoint delays that occur at the very beginning of the shipment journey.

Serves as the baseline for the 'Pickup Schedule Adherence' KPI, measuring the punctuality of carriers and shipper readiness.

Available in the appointment or scheduling data within project44, often set via the TMS.

This metric calculates the total elapsed time for each shipment case. It is typically measured from 'Shipment Created' to 'Payment Processed' to represent the full end-to-end process.

Average Shipment Cycle Time is a headline KPI for overall process efficiency. Analyzing the distribution of cycle times helps identify outliers and understand what drives long-running cases. This calculated metric is fundamental for the 'End-to-End Shipment Performance Overview' dashboard and for high-level process health monitoring.

Measures the overall end-to-end efficiency of the transportation process, providing a high-level KPI for performance tracking.

This attribute is not in the source system. It is calculated by subtracting the timestamp of the first event from the timestamp of the last event for each unique Shipment ID.

This attribute provides a snapshot of the shipment's current state in the process, such as 'In Transit', 'Delivered', or 'Exception'. It often reflects the last major activity that occurred.

While process mining derives the flow from activities, a status attribute is useful for filtering and creating high-level summary dashboards. For example, an operational dashboard might focus only on shipments with an 'In Transit' status. It provides a quick way to segment and categorize shipments without analyzing the full event history.

Provides a current-state summary of a shipment, which is useful for filtering, reporting, and operational monitoring dashboards.

A standard field in project44 that summarizes the shipment's progress based on the latest event.

This calculated metric measures the in-transit portion of the shipment lifecycle. It is calculated as the time difference between the 'Goods Picked Up' and 'Goods Delivered' activities.

This KPI is used to evaluate the efficiency of the core transportation leg, excluding pre-transit planning and post-delivery administration. It helps in assessing carrier speed, route efficiency, and the impact of in-transit delays. It is a key metric for the 'Carrier Performance and Compliance' dashboard.

Isolates the performance of the actual transportation phase, allowing for a focused analysis of carrier and route efficiency.

This attribute is not in the source system. It is calculated by finding the duration between the 'Goods Picked Up' and 'Goods Delivered' events for each shipment.