Your Supply Chain Management Data Template

The Activity Name describes a single step or task executed as part of the logistics order's lifecycle. These events are recorded chronologically to build a sequence of actions for each case.

Analyzing activities is the foundation of process mining. It allows for the visualization of the process map, detection of bottlenecks between specific steps, analysis of activity frequencies, and identification of deviations from the standard process flow.

This attribute defines the steps in the process map, making it possible to visualize, analyze, and optimize the flow of logistics orders.

Activity names are derived from event logs, transaction codes, or status changes recorded in various Blue Yonder modules related to warehousing, transportation, and order management.

The Logistics Order is the core identifier that connects all related activities from customer order creation to final delivery. Each unique Logistics Order number represents a single instance of the supply chain process.

In process mining, analyzing data by Logistics Order allows for a complete view of the order lifecycle. This is essential for calculating end-to-end cycle times, identifying process variants, and understanding the journey of each order through different stages like procurement, production, and distribution.

This is the fundamental Case ID. It links all process steps together, enabling the reconstruction and analysis of the entire order fulfillment journey.

This identifier is typically found in the main order management or logistics execution modules within Blue Yonder.

The Event Time, or Start Time, is the precise date and time that an activity was recorded in the source system. This chronological data is critical for sequencing events correctly and for all time-based analysis.

This timestamp is used to calculate cycle times between activities, measure the duration of the entire process, and identify delays or waiting times. It is the backbone for nearly all performance-related KPIs, such as End-to-End Order Lead Time and Transportation Cycle Time.

This timestamp is essential for ordering events, calculating durations, and analyzing process performance and bottlenecks over time.

This information is typically available as a creation date, change date, or posting date timestamp in the transaction data tables for each business object in Blue Yonder.

The Actual Delivery Date is captured upon the completion of the delivery, often from the 'Proof Of Delivery Signed' event. This timestamp marks the final fulfillment of the logistics order.

This attribute is essential for performance measurement. It is used in comparison with the 'Requested Delivery Date' to determine if a delivery was on-time, late, or early. This calculation is the basis for the On-Time Delivery Rate KPI and is visualized in the On-Time Delivery Performance dashboard.

Crucial for calculating the On-Time Delivery Rate, this attribute measures actual performance against the customer's expectation.

This date is often derived from the timestamp of the proof of delivery event, which can be captured in Blue Yonder's TMS or a related logistics module.

Order Status provides a snapshot of where the logistics order is in its lifecycle at the time of data extraction, or its final outcome. It's a key indicator of the case's state.

This attribute is useful for filtering analysis to focus only on completed orders or to investigate why certain orders were canceled. It helps in understanding the outcomes of different process variants and is a simple way to measure overall process success or failure rates.

Indicates the outcome of a case, allowing for analysis to be filtered for completed, in-flight, or canceled orders, which is crucial for contextualizing performance metrics.

This is typically a status field in the header of the main logistics order or shipment document in Blue Yonder.

Order Type categorizes logistics orders based on their characteristics, urgency, or business context. Different order types often follow different process paths or have different service level agreements (SLAs).

Analyzing by Order Type is crucial for understanding process variations. For example, 'Rush Orders' are expected to have shorter cycle times and may skip certain steps, while 'Bulk Orders' might have longer production lead times. This attribute helps explain why certain cases deviate from the norm and is useful in the 'Process Variant Analysis' dashboard.

Helps explain process variations and differences in performance, as different order types often have unique paths, priorities, and SLAs.

This information is typically stored in the order header data within Blue Yonder's order management system.

The Requested Delivery Date is a critical piece of customer master data associated with a logistics order. It represents the commitment made to the customer and serves as the primary benchmark for measuring delivery performance.

This date is compared against the 'Actual Delivery Date' to calculate the On-Time Delivery Rate KPI. It is fundamental for the 'On-Time Delivery Performance' dashboard, allowing for analysis of delays and their root causes, such as carrier performance or internal bottlenecks.

This is the baseline for measuring customer satisfaction and delivery performance. It's essential for calculating the On-Time Delivery Rate KPI.

This is typically stored in the customer order header data within Blue Yonder's order management system.

The Supplier Name identifies the vendor from whom goods were procured as part of the supply chain process. This is a key dimension for analyzing the inbound logistics and procurement stages.

This attribute is used in the 'Supplier Inbound Performance' dashboard to break down cycle times from purchase order creation to material receipt by each supplier. This analysis helps identify reliable and fast suppliers versus those who consistently cause delays, informing procurement strategy and supplier relationship management.

Allows for performance analysis of different suppliers, which is critical for optimizing inbound logistics and ensuring production schedules are met.

This information is stored in the purchase order header data and linked from a supplier master data table within Blue Yonder or an integrated ERP.

This attribute identifies the employee or system user responsible for a particular process step. It is essential for understanding resource allocation, workload distribution, and performance at an individual or team level.

In analysis, User Name is used to filter process maps to see how different users perform the same task, identify training needs, or pinpoint top performers. It's also critical for the 'Manual Task and Automation Potential' dashboard to see which users are involved in frequent, repetitive tasks.

Attributes user actions to specific individuals, enabling workload analysis, performance comparison, and identification of automation opportunities.

Typically found in transaction data as a 'Created By' or 'Changed By' field, linking to a user master data table in Blue Yonder.

The Carrier Name identifies the logistics partner that handled the transportation of goods from the warehouse to the final destination. It is a critical dimension for evaluating outbound logistics performance.

In the 'Transportation Efficiency Monitor' dashboard, analyzing data by Carrier Name helps compare the 'Goods In Transit' duration for different carriers. This allows the business to identify the fastest, most reliable, or most cost-effective transportation partners and optimize shipping strategies accordingly.

Enables performance benchmarking of different transportation carriers, helping to optimize shipping costs, routes, and delivery times.

This is typically found in the shipment or freight order documents within Blue Yonder's Transportation Management System (TMS).

Identifies the end customer for the logistics order. This is a fundamental dimension for segmenting analysis from a customer-centric view.

Analyzing process performance by customer can reveal if certain customers experience longer lead times or more issues. This attribute supports dashboards like 'On-Time Delivery Performance' by allowing a breakdown by customer, helping to prioritize improvements for key accounts.

Enables customer-centric analysis, helping to identify which customers are most affected by process inefficiencies and to prioritize service improvements.

This information is stored in the customer order header data and is linked from a customer master data table in Blue Yonder or an integrated CRM/ERP.

The End Time marks the conclusion of an activity. When both a Start Time and End Time are available, the precise processing time of an activity can be calculated, distinguishing it from idle or wait time.

This is highly valuable for analyzing the duration of specific tasks, such as 'Goods Picked and Packed' or 'Quality Control Performed'. It helps pinpoint which activities are consuming the most time, supporting targeted optimization and automation efforts.

Enables accurate calculation of activity processing time, which is key to identifying inefficient tasks and measuring resource productivity.

Like the start time, this is typically found as a timestamp in the transaction data tables for each business object in Blue Yonder, often marking a status completion.

This metric measures the total duration of a logistics order's lifecycle. It is a key performance indicator that reflects the overall speed and efficiency of the entire supply chain process.

This is the primary metric for the 'End-to-End Order Lead Time Analysis' dashboard and the 'Logistics Order End-to-End Cycle Time' KPI. Analyzing this duration helps identify systemic delays and provides a high-level measure of process health. It can be broken down by dimensions like Order Type or Product Category to find drivers of long lead times.

This is a critical KPI for measuring the overall velocity of the supply chain, directly impacting customer satisfaction and working capital.

This value is not stored in the source system. It is calculated by subtracting the timestamp of the first event from the timestamp of the last event for each case.

This is a boolean attribute derived by comparing the 'Actual Delivery Date' to the 'Requested Delivery Date'. It simplifies performance analysis by categorizing every order as either 'On-Time' (true) or 'Late' (false).

This attribute directly powers the 'On-Time Delivery Performance' dashboard and is used to calculate the 'On-Time Delivery Rate' KPI. It allows for quick filtering and root cause analysis to understand the common factors, such as carrier or product type, associated with late deliveries.

Simplifies on-time delivery analysis by providing a clear boolean outcome for each order, making it easy to calculate performance rates and identify drivers of delays.

This attribute is not in the source system. It is calculated during data transformation using the formula: ActualDeliveryDate <= RequestedDeliveryDate.

This boolean flag is set to true if a logistics order shows evidence of rework loops, such as the activity sequence 'Goods Picked and Packed' -> 'Quality Control Performed' -> 'Goods Picked and Packed'. It identifies cases that deviate from the standard, efficient flow.

This attribute is used to calculate the 'Order Rework Rate' KPI and is visualized in the 'Process Variant and Rework Analysis' dashboard. Pinpointing cases with rework helps identify sources of errors or inefficiency in the fulfillment process, leading to targeted improvements to reduce waste and operational costs.

Highlights process inefficiencies and quality issues by flagging cases with repeated steps, enabling focused efforts to improve process stability and reduce costs.

This is not a field in Blue Yonder. It is calculated during process mining analysis by detecting specific repeated sequences of activities within a case.

This attribute provides the date and time of the most recent data pull. It gives context to the analysis, showing how current the data is and when the next refresh might be expected.

It is important for users to understand the freshness of the data they are analyzing. This helps in interpreting dashboards and ensuring that decisions are based on timely information.

Provides crucial context on data freshness, ensuring users are aware of how up-to-date the process analysis is.

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

This attribute specifies the transportation mode used to move goods. Different modes have varying costs, speeds, and capacities, making this an important factor in logistics planning and analysis.

The 'Transportation Efficiency Monitor' dashboard uses this attribute to compare transit times and costs across different transport modes. This helps in making strategic decisions, such as choosing between faster but more expensive air freight versus slower but cheaper sea freight, based on the order's priority and cost constraints.

Provides a key dimension for analyzing transportation costs and speed, enabling strategic decisions on the most effective shipping methods.

This information is usually stored within the shipment or freight order details in Blue Yonder's TMS.

Product Category is a classification used to group similar products together. Different product categories may have distinct supply chain processes, handling requirements, or lead times.

This attribute is used in the 'Logistics Order Throughput Trend' dashboard to filter and compare the volume of completed orders for different types of products. It can reveal if certain product lines are facing more delays or have lower throughput, helping to focus improvement efforts where they are most needed.

Allows for segmenting the process analysis by product type, revealing category-specific bottlenecks, demand patterns, or handling complexities.

This is part of the material or product master data, which would be linked to the line items of the logistics order in Blue Yonder.

The Purchase Order Number links the logistics order to the procurement process. It is created during activities like 'Purchase Requisition Created' and 'Purchase Order Issued'.

This attribute allows for a detailed analysis of the procurement sub-process. It's essential for the 'Supplier Inbound Performance' dashboard, where it helps track the journey of a specific PO from issuance to the receipt of goods, associating delays with specific suppliers or materials.

Links the main fulfillment process to the upstream procurement activities, enabling detailed analysis of supplier performance and procurement cycle times.

This identifier is generated and stored in the procurement or purchasing module of Blue Yonder or an integrated ERP system.

This attribute identifies the person or team that created the purchase requisition, which is the internal document that triggers the creation of a formal purchase order. It provides context on who is driving procurement demand within the organization.

Analyzing by this attribute helps in understanding internal procurement patterns and can be used in the 'Manual Task and Automation Potential' dashboard. If a few users are creating a high volume of standard requisitions, it might indicate an opportunity for automating the requisitioning process.

Identifies the origin of a procurement request, which helps in analyzing internal demand patterns and identifying opportunities for process automation.

Found in the purchase requisition document data, typically as a 'Created By' field.

This attribute identifies the origin of the process data. It is particularly useful in environments where data from multiple systems is combined for a holistic process view, ensuring clear data lineage.

For this analysis, the value will consistently be 'Blue Yonder', but it serves as a crucial piece of metadata for data governance and context, especially if other systems like an ERP or CRM are integrated.

Identifies the data's origin, which is crucial for data governance, validation, and managing analyses that span multiple enterprise systems.

This is typically a static value added during the data extraction and transformation process to label the dataset's origin.

This date is the supplier's commitment for when raw materials or components will be delivered. It is the benchmark used to measure the reliability and timeliness of a supplier.

This attribute is essential for calculating the 'Supplier On-Time Delivery Rate' KPI. It is compared with the actual receipt date of the materials ('Raw Materials Received' event timestamp) to determine if the supplier met their commitment. This analysis is central to the 'Supplier Inbound Performance' dashboard.

Acts as the performance benchmark for inbound deliveries, enabling the measurement of supplier reliability and its impact on the production schedule.

This date is typically stored at the purchase order line item level, based on information provided by the supplier or standard lead times.