Your Supply Chain Management Data Template

The Activity represents a distinct step or task performed within the supply chain process. Each activity marks a specific point in the lifecycle of a logistics order, providing the building blocks for the process map.

Analyzing activities allows organizations to understand what steps are actually being performed, in what sequence, and how frequently. This view helps identify bottlenecks, redundant steps, and deviations from the standard operating procedure. Common activities in supply chain include order creation, goods receipt, picking, packing, shipping, and invoicing.

This attribute forms the backbone of the process map, allowing for the visualization and analysis of the sequence of steps in the supply chain.

Often derived from event logs, status change records, document types, or transaction codes in the source system.

The Case ID represents the unique instance of a process being analyzed. In Supply Chain Management, this is typically the logistics order number, which links all related activities from initial creation to final delivery.

This attribute is essential for grouping all related events, such as purchase order creation, goods shipment, and customer invoicing, into a single end-to-end process flow. By tracking this identifier, analysts can visualize the complete journey of an order, measure its total cycle time, and identify variations between different order paths. Without a consistent Case ID, it is impossible to reconstruct the process flow accurately.

It is the fundamental attribute for process mining, as it connects all related activities into a single case, enabling the analysis of the end-to-end process flow.

Typically found in the header data of primary business documents like sales orders, delivery notes, or overarching logistics order tables.

The Start Time is a precise timestamp, including date and time, that marks the beginning of an activity. It is a critical component for chronological ordering of events and for performance analysis.

This attribute is fundamental for calculating cycle times, identifying delays between steps, and understanding the overall duration of the process. By analyzing timestamps, businesses can measure throughput, pinpoint bottlenecks where cases wait for long periods, and evaluate performance against service level agreements. Accurate timestamps are the foundation of any time-based process mining analysis.

It enables the chronological sequencing of activities and is essential for all time-based calculations, such as cycle times and bottleneck analysis.

Usually found in event logs, transaction records, or document creation timestamps in the source system's transactional tables.

This attribute records the date and time of the most recent data extraction or update for a given event record. It is a technical attribute used to ensure data freshness and reliability.

While not typically used for direct process analysis, Last Data Update is critical for dashboard monitoring and data governance. It helps users understand how current the displayed information is and can be used to set up alerts for data pipeline failures. This ensures that business decisions are being made based on timely and relevant data.

It is essential for data governance and monitoring, allowing users to verify the freshness of the analysis and trust the insights provided.

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

The Source System attribute identifies the application or database where the event data originated. In complex supply chain environments, data often comes from multiple systems, such as an ERP, a Warehouse Management System (WMS), and a Transportation Management System (TMS).

Tracking the source system is important for data governance, validation, and understanding the context of an activity. It helps in troubleshooting data quality issues and can be used in analysis to compare processes that span different systems or to identify activities that are exclusively handled by a specific application. This information provides a technical context for the business process.

It provides crucial context about data origin, which is vital for data validation and for analyzing processes that span multiple enterprise systems.

This information is often part of the data extraction layer or can be a static value assigned based on the data source connection.

The Actual Delivery Date marks the final timestamp in the order fulfillment lifecycle, capturing the moment the goods were received by the customer. This is often confirmed through a proof of delivery document or a status update from the carrier.

This attribute is essential for calculating actual end-to-end cycle times and for performance measurement. When compared against the Requested Delivery Date, it directly determines whether an order was early, on-time, or late. Analyzing this data helps identify systemic causes of delays, whether they originate in procurement, production, or logistics, and provides the factual basis for improving delivery reliability.

It provides the factual endpoint for measuring actual cycle times and is used with the requested date to determine on-time delivery performance.

Sourced from transportation management systems (TMS), carrier updates, or proof of delivery records.

The Customer Identifier is a unique code or number assigned to each customer. This attribute links a logistics order to the specific entity that will receive the goods and payment.

This attribute is a key dimension for segmenting and analyzing the order-to-cash process. It allows businesses to evaluate performance metrics, such as on-time delivery and order cycle time, for different customer groups or key accounts. This analysis can reveal which customers experience the most delays or which have unique process variations. These insights are valuable for improving customer service and tailoring logistics operations to meet specific needs.

It allows for customer-centric analysis, enabling segmentation of performance metrics like cycle time and on-time delivery by customer.

Found in sales order header data or customer master data within an ERP or CRM system.

The End Time is a precise timestamp that marks the completion of an activity. When both a Start Time and End Time are available for an event, it becomes possible to measure its processing time directly.

This attribute allows for a more granular analysis of performance. Instead of only measuring the waiting time between activities, analysts can differentiate between active processing time and idle time. This is particularly useful for identifying inefficient activities that consume significant resources, such as long packing durations or extended quality inspection times. This level of detail supports targeted operational improvements.

It enables the calculation of activity processing time, which helps distinguish between value-adding time and waiting time for more precise bottleneck analysis.

Found in event logs or transactional tables where both start and completion timestamps for tasks are recorded.

The Product Identifier, often a Stock Keeping Unit (SKU) or material number, uniquely identifies the item being procured, produced, and delivered. A single logistics order can involve one or multiple product identifiers.

Analyzing the supply chain process by product reveals how different items flow through the system. It can highlight products that have longer production lead times, higher quality inspection failure rates, or are more prone to shipping delays. This product-level view is essential for inventory management, demand forecasting, and optimizing production and logistics strategies for different product families.

This enables product-level analysis of the process, helping to identify which products have longer cycle times or are associated with more process exceptions.

Found in the line-item details of sales orders, purchase orders, or production orders.

The Requested Delivery Date is the target date by which the goods are expected to arrive at the customer's location. This date is typically set by the customer at the time of order placement or determined by internal planning processes.

This attribute serves as the primary baseline for measuring on-time delivery performance, a critical KPI in supply chain management. By comparing the Requested Delivery Date with the Actual Delivery Date, companies can calculate their On-Time In-Full (OTIF) rate, identify reasons for delays, and analyze performance trends across different regions, customers, or product types. It is fundamental for assessing customer satisfaction and supply chain reliability.

It is the baseline for calculating On-Time Delivery Rate, one of the most critical KPIs for measuring supply chain performance and customer satisfaction.

Found in sales order header data or planning documents within the ERP or order management system.

The Supplier Identifier is a code or number that uniquely identifies a vendor or supplier involved in the procurement stage of the supply chain. This ID links purchase orders and goods receipt activities to a specific supplier.

Analyzing process performance by supplier is crucial for effective vendor management. It allows businesses to measure supplier on-time delivery rates, lead times, and quality inspection pass rates. These insights can inform supplier scorecards, contract negotiations, and decisions about supply chain diversification to mitigate risks. By segmenting the process by supplier, companies can identify top-performing partners and those that cause delays.

It enables supplier performance analysis, helping to measure lead times, on-time delivery rates, and quality, which is crucial for procurement optimization.

Found in purchase order documents or supplier master data within an ERP or procurement system.

The User Name attribute identifies the individual, department, or system agent responsible for performing a specific task in the process. This could be a warehouse operator who completes picking or a system bot that automatically creates a purchase order.

Analyzing process performance by user or team helps uncover variations in efficiency, identify training needs, and highlight best practices. For example, it can reveal which teams have the shortest processing times or which users most frequently deviate from the standard process. It is also valuable for compliance and auditing purposes to track who performed critical actions.

This attribute adds a human or system resource dimension to the analysis, enabling performance comparison, workload balancing, and compliance tracking.

Available in transaction logs or document change history, often linked to user master data.

The Mode of Transport specifies the logistics method used to move goods from the origin to the destination. This could include options like road, rail, air, or sea freight.

Analyzing the process by mode of transport helps in optimizing logistics costs and performance. For example, it can reveal the actual transit times for air freight versus sea freight, allowing for a data-driven cost, benefit analysis. It also helps identify if certain transport modes are more prone to delays or damage, supporting better carrier and route planning.

It provides a key dimension for analyzing transportation costs and delivery times, helping to optimize logistics strategies.

Found in shipment documents, delivery orders, or transportation management system (TMS) records.

The Order Status provides a snapshot of where the logistics order is in its lifecycle at the end of the process or at the time of data extraction. It typically reflects the final outcome of the case.

This attribute is primarily used for outcome analysis. By filtering for cases with a 'Canceled' status, for example, analysts can investigate the root causes of order cancellations. Similarly, analyzing 'Partially Fulfilled' orders can reveal issues with inventory accuracy or supplier reliability. Understanding the distribution of final statuses is key to measuring overall process success.

It is crucial for outcome analysis, allowing for filtering and investigation of cases based on their final state, such as completed, canceled, or delayed.

Available in the header data of the primary order document (e.g., sales order, logistics order).

The Order Type categorizes logistics orders based on their nature, priority, or fulfillment strategy. Common types include standard, express, replenishment, or special project orders.

This attribute is a powerful filter for comparative analysis. By comparing the process flows of rush orders versus standard orders, a business can assess whether expedited processes are truly faster or if they introduce inefficiencies and higher costs. It also helps in understanding if different order types follow distinct process paths and allows for the optimization of each path independently.

It allows for process comparison between different types of orders, helping to understand if certain categories are more prone to delays or rework.

Typically stored in the header data of sales orders or logistics orders.

The Origin Location identifies the physical site, such as a distribution center, manufacturing plant, or supplier warehouse, from which goods begin their journey. It represents the starting point of a key logistics leg in the supply chain.

Analyzing the process by origin location helps identify performance variations between different facilities. It can highlight which plants have longer production lead times or which distribution centers are more efficient at picking and packing. This geographical or site-specific analysis is vital for network optimization, resource allocation, and standardizing best practices across the organization.

It enables performance comparison across different plants or warehouses, helping to identify operational bottlenecks and best practices at specific sites.

Found in inventory management, warehouse management, or transportation systems, often associated with shipment or production order data.

The Purchase Order Number is the unique identifier for the document used to procure goods or services from an external supplier. It is a key link between the overall logistics order and the specific procurement activities.

This attribute allows analysts to drill down into the procurement subprocess. It helps in tracking the lifecycle of a purchase from requisition to goods receipt, measuring supplier lead times accurately, and identifying bottlenecks in the purchasing approval or fulfillment process. It can also be used to correlate procurement issues with downstream delays in production or customer delivery.

It links the end-to-end process to specific procurement activities, enabling detailed analysis of the procure-to-pay subprocess and supplier performance.

Stored in purchasing document headers and referenced in related documents like goods receipts and supplier invoices.

The Sales Order Number is the unique identifier for the document that initiates the fulfillment process based on a customer request. It serves as a primary reference throughout the order-to-cash cycle.

In scenarios where the main Case ID is a consolidated logistics order, the Sales Order Number provides a crucial link back to the specific customer demand. It enables analysis of the process from a sales view, helping to measure order processing times, fulfillment rates, and the time taken from order creation to final delivery. It is essential for connecting supply chain operations directly to customer transactions.

It connects logistics activities to the initial customer demand, enabling a clear view of the order-to-cash process and customer fulfillment performance.

Stored in sales document headers and referenced in subsequent documents like deliveries and invoices.