Your Transportation Management Data Template

The Activity Name describes a specific step or status change within the transportation process. These events form the sequence of the process map, showing how a shipment progresses from creation to completion.

Analyzing activities is core to process mining. It helps visualize the process flow, identify common and rare pathways, discover rework loops like repeated booking attempts, and measure the frequency of each step. The sequence and timing of these activities are used to calculate cycle times and identify bottlenecks between stages.

This attribute defines the steps in the process, forming the basis of the process map and enabling the analysis of process flow, variations, and bottlenecks.

Typically derived from event logs, status change tables, or specific transaction records within Trimble TMS that are linked to a shipment.

Event Time is the precise date and time recorded for each activity in the shipment's lifecycle. It provides the chronological order of events, which is essential for constructing the process flow and performing any time-based analysis.

This attribute is fundamental for all process mining analytics. It is used to calculate cycle times between activities, measure the total duration of a case, identify waiting times, and analyze process performance over different time periods. Accurate timestamps are critical for diagnosing delays and understanding process efficiency.

It provides the chronological sequence of events, which is essential for calculating all duration-based metrics like cycle times and identifying process delays.

Located alongside the activity or status field in event logs or transaction tables within Trimble TMS.

The Shipment ID is the central case identifier that groups all events and activities related to a single transportation order. Each shipment represents a complete journey, from initial creation and planning through execution, delivery, and financial settlement.

In process mining, analyzing the process by Shipment allows for a holistic view of the end-to-end transportation lifecycle. This enables the measurement of total cycle times, identification of bottlenecks affecting specific shipments, and comparison of process paths for different types of shipments. It is the fundamental attribute for tracking a single order through the entire system.

It is the essential case identifier that connects all related activities, allowing for a complete end-to-end analysis of each transportation order.

This is the primary key in the main shipment or order tables within Trimble TMS. Consult Trimble TMS documentation for specific table and field names.

This attribute shows the date and time when the data was last extracted or updated from Trimble TMS. It provides context on the freshness of the data being analyzed.

In any analysis, understanding the recency of the data is crucial for making timely and relevant business decisions. This timestamp helps users trust the data and understand the time window covered by the current analysis, ensuring they are not acting on outdated information.

Indicates the freshness of the data, ensuring that analyses are based on up-to-date information for accurate decision-making.

This timestamp is typically generated and recorded by the ETL (Extract, Transform, Load) tool during the data ingestion process.

This attribute identifies the source application where the data originated. In this context, it would typically be 'Trimble TMS'. In more complex environments, it could differentiate between different modules or integrated systems, like a separate financial system for payments.

Specifying the source system is important for data governance and traceability. It helps in understanding the context of the data and is crucial when merging data from multiple sources to create a single end-to-end process view.

Ensures data traceability and context, which is critical when data from multiple systems is combined to analyze the end-to-end process.

This is often a static value added during the data extraction process to label the origin of the records.

The Carrier Name identifies the third-party logistics provider or internal fleet assigned to execute the transportation of the goods. This is a critical piece of master data associated with each shipment.

This attribute is essential for performance analysis, particularly for the Carrier Performance & Compliance dashboard. By segmenting the process data by Carrier Name, businesses can compare on-time delivery rates, average cycle times, and delay frequencies among different providers. This helps in negotiating contracts, selecting reliable partners, and improving the overall supply chain.

Allows for performance benchmarking and compliance analysis across different transportation providers, directly supporting carrier management and selection.

Found in the main shipment or load tables in Trimble TMS, often linked from a carrier master data table.

The Delay Reason provides context for why a shipment did not meet its scheduled timeline. Reasons can range from 'Carrier Delay' and 'Customs Hold' to 'Weather' or 'Customer Not Available'. This information is often manually entered or selected from a predefined list when a delay is recorded.

This attribute is invaluable for root cause analysis, especially for the Shipment Delay & Reason Analysis dashboard. By categorizing delays, businesses can identify recurring problems, whether they are with specific carriers, routes, or internal processes. This allows for targeted improvement initiatives to reduce delays and improve reliability.

Enables root cause analysis of delays, helping to identify recurring issues with carriers, routes, or processes that can be targeted for improvement.

May be stored in a specific delay or exception logging table, or as a free-text note field on the shipment record in Trimble TMS.

The End Time marks the completion of an activity. When available, it can be used with the Start Time to calculate the precise processing time for a single step, distinguishing it from the waiting time before the next step begins.

In analysis, having both a start and end time for activities allows for a more granular view of process performance. It helps differentiate between active work time (processing time) and idle time (waiting time), which is key to identifying true efficiency gains versus resource or scheduling delays. For example, it can measure the exact duration of the 'Freight Bill Audited' activity.

Enables the precise calculation of activity processing time, separating active work duration from waiting time between process steps.

Some modules in Trimble TMS may log both a start and end event for certain activities. This needs to be verified in the event or transaction logs.

This is a calculated flag that compares the 'ActualDeliveryDate' with the 'RequestedDeliveryDate'. It evaluates to true if the actual delivery occurred on or before the requested date, and false otherwise.

This attribute simplifies performance analysis and dashboard creation. Instead of comparing dates directly in every chart, this flag allows for easy filtering and aggregation to calculate the Shipment On-Time Delivery Rate KPI. It provides a clear, binary outcome for each shipment's delivery performance, making it easy to visualize success rates.

Simplifies the calculation of on-time delivery KPIs and allows for easy filtering and segmentation of on-time versus late shipments.

This attribute is not in the source system. It is calculated during data transformation by comparing 'ActualDeliveryDate' <= 'RequestedDeliveryDate'.

Mode of Transport specifies the transportation method employed for the shipment. This could include Full Truckload (FTL), Less Than Truckload (LTL), air freight, ocean cargo, or rail.

Analyzing the process by Mode of Transport is crucial for strategic decision-making and cost optimization. It allows for comparing the efficiency, speed, and cost-effectiveness of different modes. For instance, the Mode of Transport Efficiency Comparison dashboard uses this attribute to show which modes have longer in-transit times or higher delay rates, helping planners make better choices.

Enables comparison of cost, speed, and efficiency across different transportation methods, supporting strategic route and mode planning.

This is a standard field on the shipment or load record within Trimble TMS.

The Requested Delivery Date is the target date by which the shipment is expected to be delivered to its final destination. This date serves as the primary benchmark for measuring on-time performance.

This attribute is critical for calculating key performance indicators like the Shipment On-Time Delivery Rate. By comparing the actual delivery timestamp with this requested date, the system can determine if a shipment was early, on-time, or late. This is fundamental for the Actual vs Requested Delivery Performance dashboard and for evaluating customer satisfaction and carrier reliability.

Serves as the baseline for measuring on-time delivery performance, a critical KPI for customer satisfaction and operational excellence.

Located in the order or shipment details tables within Trimble TMS.

The Actual Delivery Date is the timestamp marking the completion of the delivery. It represents the ground truth of when the shipment reached its destination. This is typically the timestamp of the 'Goods Delivered' event.

This attribute is used in conjunction with the Requested Delivery Date to determine on-time status. It is the factual endpoint for many cycle time calculations and performance measurements, directly feeding into KPIs that track delivery performance and carrier reliability. It is a cornerstone for analyzing actual process execution against planned schedules.

Provides the factual completion time of the delivery, enabling the calculation of on-time performance and actual transit times.

This is the timestamp associated with the 'Goods Delivered' event status in the shipment's event log.

The Customer Name identifies the client or business entity that owns the goods being shipped or is the recipient of the service. This is a key piece of master data for segmenting the analysis.

Analyzing the transportation process by customer can reveal important insights. It helps determine if certain customers experience more delays, require more rework during booking, or have unique process flows. This information can be used to improve customer service, tailor logistics solutions, and manage key accounts more effectively.

Allows for customer-centric process analysis, helping to identify if specific clients face unique challenges or require different service levels.

Found in the main order or shipment tables, often linked from a customer master data table.

The Destination Country is the country of the shipment's final delivery address. Similar to the origin country, it is a key attribute for geographical process analysis.

Analyzing data by destination country helps uncover location-specific process issues. For example, shipments going to a certain country might consistently face longer customs clearance times or delivery delays. This insight allows for proactive planning and adjustment of delivery timelines for specific routes, improving the accuracy of delivery promises.

Helps pinpoint process challenges specific to destination regions, such as customs delays or final-mile delivery issues.

Derived from the destination address information stored in the shipment or order details within Trimble TMS.

Event Duration measures the processing time of an activity, calculated as the difference between its End Time and Start Time. This metric represents the active work time for a specific process step.

This calculated attribute is vital for distinguishing between active processing time and passive waiting time. For example, it can show that the 'Freight Bill Audited' activity itself only takes 30 minutes, but there is an average wait of 2 days before it begins. This insight helps focus improvement efforts on the right areas, such as reducing queue times rather than trying to speed up an already efficient task.

Measures the active processing time of an activity, helping to differentiate actual work from idle waiting time for more precise bottleneck analysis.

Calculated by subtracting the 'EventTime' (StartTime) from the 'EndTime' attribute for each event.

The Freight Bill Amount is the invoiced cost for transporting the shipment. This financial data is crucial for cost analysis and understanding the financial impact of process inefficiencies.

In process mining, this attribute allows for the analysis of costs associated with different process variants, carriers, or routes. For example, it can be used to determine if shipments with frequent rework or delays tend to have higher associated costs. It is also essential for analyses related to freight bill auditing and payment processing.

Connects process execution to financial outcomes, enabling analysis of how process variations, delays, or carrier choices impact transportation costs.

Found in the freight billing or financial settlement modules of Trimble TMS, linked to the shipment.

Freight Bill Status tracks the progress of an invoice through the financial settlement part of the transportation process. It indicates whether a bill has been received, is under review, has been approved, rejected for correction, or paid in full.

This attribute is essential for the Freight Bill Auditing & Payment Speed dashboard. It helps to measure the cycle time of the auditing process, identify bottlenecks in payment approvals, and quantify the Freight Bill Rejection Rate. Analyzing these statuses can reveal inefficiencies in the procure-to-pay subprocess.

Provides visibility into the financial settlement process, helping to measure auditing efficiency and identify reasons for payment delays or disputes.

Located in the accounts payable or freight settlement module of Trimble TMS.

This is a calculated flag that is set to true if a shipment has an associated delay reason or if its status indicates a delay. It differs from 'IsOnTime' as a shipment can be delayed but still arrive on time through corrective action.

This attribute helps in focusing analysis on only those shipments that encountered exceptions. It is used in the Shipment Delay & Reason Analysis dashboard to isolate problematic cases and analyze the root causes without the noise of smoothly processed shipments. It helps quantify the frequency of operational exceptions.

Identifies shipments that have encountered operational exceptions, allowing for focused analysis on the causes and impacts of these delays.

Calculated during data transformation. The logic would be to set the flag to true if the 'DelayReason' field is not null or if a specific 'delay' activity is present.

The Origin Country is the country of the shipment's starting point. This geographical information is key for analyzing logistics on a global or regional scale.

This attribute allows for segmenting process performance by geography. It can help identify if cycle times or delay rates are higher for shipments originating from certain countries, which may point to specific regional challenges like customs complexity or infrastructure issues. It is particularly important for analyzing customs clearance bottlenecks.

Allows for geographical analysis of process performance, helping to identify regional bottlenecks, especially related to customs or transit times.

Derived from the origin address information stored in the shipment or order details within Trimble TMS.

This is a calculated metric that measures the time it takes to receive and process the proof of delivery (POD) documentation after the physical delivery has been completed. A long POD cycle time can delay invoicing and impact cash flow.

This attribute is the basis for the Proof of Delivery Receipt Lag dashboard and its corresponding KPI. By calculating this duration for each shipment, the business can identify bottlenecks in the POD process, such as slow submission by carriers or inefficient internal processing, and take action to accelerate customer billing.

Directly measures the efficiency of the administrative process following delivery, which is critical for timely invoicing and healthy cash flow.

Calculated by finding the timestamp difference between the 'Proof of Delivery Received' and 'Goods Delivered' activities for each shipment.

Shipment Status indicates the latest known state of the shipment in its lifecycle, such as 'Planned', 'In Transit', 'Delivered', or 'Cancelled'. It provides a snapshot of where the shipment is at any given time.

While process mining reconstructs the historical flow, the current status is useful for filtering and analyzing ongoing cases. It helps in segmenting the data to focus on open shipments versus completed ones, or to investigate why a high number of shipments are stuck in a particular status. It provides valuable context for operational monitoring.

Provides a current snapshot of the shipment's progress, allowing for the analysis and filtering of open, completed, or problematic cases.

A standard field on the header of the main shipment or load table in Trimble TMS.

Total Cycle Time measures the end-to-end duration for each shipment case. It is calculated by taking the difference between the timestamp of the very first activity (e.g., 'Shipment Created') and the very last activity (e.g., 'Payment Processed').

This is a primary KPI for measuring overall process efficiency. It provides a high-level view of performance for the Overall Shipment Throughput & Cycle Time dashboard. Analyzing how this metric trends over time or how it varies by carrier, route, or mode of transport helps identify broad areas for strategic improvement.

Measures the overall end-to-end process velocity, providing a key indicator of efficiency and customer experience.

Calculated at the case level by subtracting the minimum timestamp from the maximum timestamp for all events within a single 'Shipment' case.

The User Name identifies the individual employee or automated system responsible for executing a process step, such as planning a shipment, auditing a freight bill, or processing a payment. It links process activities to human or system resources.

Analyzing data by user helps in understanding workload distribution, identifying training needs, and spotting performance outliers. For instance, in the Shipment Booking Rework & Errors dashboard, this attribute can help pinpoint if rework is concentrated among specific users, suggesting a need for additional training or process clarification. It is also key for compliance and auditing purposes.

Links process activities to specific employees or system users, enabling workload analysis, performance evaluation, and identification of training opportunities.

Typically found in transaction or event logs, associated with the user ID that created or modified the record.