Your Supply Chain Management Data Template
Your Supply Chain Management Data Template
- Recommended attributes to collect
- Key activities to track
- Extraction guidance for Kinaxis RapidResponse
Supply Chain Management Attributes
| Name | Description | ||
|---|---|---|---|
| Activity Name ActivityName | The name of the specific business event or step that occurred within the logistics process, such as 'Goods Shipped' or 'Purchase Order Issued'. | ||
| Description This attribute describes a single step or milestone in the supply chain process. It captures key events like order creation, inventory checks, production stages, and delivery confirmations, forming the sequence of operations for each Logistics Order. In process mining analysis, the sequence of activities is used to automatically discover the process map, identify deviations from the standard procedure, and pinpoint bottlenecks. It is the foundation for analyzing process flow, conformance, and identifying rework loops, as seen in the Quality Control Rework Analysis dashboard. Why it matters It defines the steps of the process, allowing for the discovery and visualization of the actual end-to-end supply chain flow. Where to get This is typically derived from event logs, status change records, or transaction codes within various modules of Kinaxis RapidResponse. Examples Purchase Order IssuedRaw Materials ReceivedGoods ProducedGoods Shipped | |||
| Event Time EventTime | The timestamp indicating when a specific activity or event occurred, with date and time information. | ||
| Description The Event Time records the exact moment an activity took place. This timestamp is crucial for ordering events chronologically and calculating durations between different steps in the process. Analysis heavily relies on this attribute to calculate all time-based metrics, including cycle times, waiting times, and lead times. It is essential for dashboards like Order Fulfillment Cycle Time and KPIs such as Avg Order-to-Delivery Cycle Time. Accurate timestamps are the basis for understanding process performance and identifying delays. Why it matters This timestamp provides the chronological order of events and is the basis for all duration and performance calculations, revealing bottlenecks and delays. Where to get This information is typically found alongside activity data in transaction logs or status update records across Kinaxis RapidResponse modules. Examples 2023-10-26T08:00:00Z2023-10-26T14:30:15Z2023-10-27T10:05:00Z | |||
| Logistics Order LogisticsOrder | The unique identifier for a specific logistics order, linking all related activities from demand planning to final delivery. | ||
| Description The Logistics Order serves as the primary case identifier, grouping all events related to a single fulfillment journey. It allows for end-to-end tracking of a product's movement through the supply chain, from the initial forecast or customer request to the final proof of delivery. In process mining, analyzing activities by Logistics Order is fundamental. It enables the visualization of complete process flows, calculation of cycle times, and identification of variations and bottlenecks for each individual order. This is the backbone for dashboards like Order Fulfillment Cycle Time and End-to-End Logistics Variants. Why it matters This is the essential key for tracing the entire lifecycle of an order, making it possible to analyze process variations, efficiency, and compliance from start to finish. Where to get This identifier is typically a core field in order management or logistics planning modules within Kinaxis RapidResponse. Examples LO-2024-00123LO-2024-00124LO-2024-00125 | |||
| Last Data Update LastDataUpdate | The timestamp indicating the last time the data for this event was refreshed or extracted from the source system. | ||
| Description This attribute provides the date and time of the most recent data pull. It is a metadata field that helps users understand the freshness of the data they are analyzing. In any process mining dashboard, this information is critical for context. It tells the user how current the analysis is and when the next data update is expected, ensuring that decisions are made based on timely information. Why it matters Informs users about the timeliness of the data, ensuring they understand how current the process analysis is and when it was last refreshed. Where to get This is a metadata field generated and stamped onto the dataset during the data extraction, transformation, and loading (ETL) process. Examples 2024-05-20T02:00:00Z2024-05-21T02:00:00Z | |||
| Source System SourceSystem | The system of record from which the event data was extracted. | ||
| Description This attribute identifies the originating system for each event log entry. In a complex landscape, events for a single process might come from multiple systems, such as an ERP, a WMS, and Kinaxis itself. In analysis, this helps in data validation and understanding the technological landscape of the process. It can also help identify data integration issues or discrepancies between different systems involved in the supply chain. Why it matters It provides context about the data's origin, which is crucial for data validation, troubleshooting, and understanding process fragmentation across different IT systems. Where to get This is often a static value added during the data extraction process to label the origin of the data. Examples Kinaxis_RR_ProdSAP_ECCOracle_Fusion | |||
| Actual Delivery Date ActualDeliveryDate | The actual date the order was delivered to the customer, confirmed by proof of delivery. | ||
| Description This attribute records the timestamp when the customer officially received the goods. It marks the final step in the order fulfillment process. It is the counterpart to the 'Requested Delivery Date' and is used to determine if a delivery was on-time or late. This is a core metric for the On-Time Delivery Performance dashboard and is vital for calculating service level agreements (SLAs) and overall supply chain reliability. Why it matters It confirms the completion of the delivery process and is essential for calculating actual delivery performance against customer expectations. Where to get This information often comes from a proof of delivery event, which may be recorded in Kinaxis or an integrated transportation management system (TMS). Examples 2023-11-162023-11-202023-12-05 | |||
| Customer ID CustomerIdentifier | The unique identifier for the customer who placed the order. | ||
| Description This attribute identifies the end customer associated with the logistics order. It is crucial for segmenting process analysis from a customer-centric point of view. Using the Customer ID, it's possible to analyze On-Time Delivery Performance for specific customers, understand which customers have the most complex order flows, and tailor service improvements. This helps in prioritizing high-value customers and managing customer relationships more effectively. Why it matters Allows for customer-centric process analysis, helping to evaluate service levels, delivery performance, and fulfillment complexity for key accounts. Where to get Found in customer order tables or workbooks within Kinaxis RapidResponse, often labeled 'Customer Number' or 'Sold-To Party'. Examples CUST-9001CUST-9002CUST-9003 | |||
| Product ID ProductIdentifier | The unique identifier for the product associated with the logistics order, such as a SKU or material number. | ||
| Description This attribute specifies the product being handled in the logistics order. It allows for analysis to be segmented by product type, category, or specific item. Analyzing the process by product is critical for identifying items that face frequent delays, quality issues, or complex fulfillment paths. This is essential for the Demand Forecast Accuracy and Quality Control Rework Analysis dashboards, helping to pinpoint problematic product lines or supply chains. Why it matters Enables process analysis specific to product lines or categories, helping to identify which products have inefficient or problematic fulfillment paths. Where to get This is a standard field in order, shipment, and inventory data within Kinaxis RapidResponse, often labeled as 'SKU', 'Material Number', or 'Product ID'. Examples SKU-100-BLUEMAT-58930-APROD-XYZ-001 | |||
| Requested Delivery Date RequestedDeliveryDate | The delivery date for the order as requested by the customer. | ||
| Description This attribute stores the date on which the customer expects to receive their order. It serves as the baseline for measuring delivery performance and customer satisfaction. This date is directly compared against the 'Actual Delivery Date' to calculate the On-Time Delivery Rate KPI and power the On-Time Delivery Performance dashboard. Understanding the gap between requested and actual delivery dates is key to identifying systemic delays and improving customer service. Why it matters This is the primary benchmark for measuring on-time delivery performance and is a critical component of customer satisfaction KPIs. Where to get This is a standard field on customer sales orders within Kinaxis RapidResponse. Examples 2023-11-152023-11-202023-12-01 | |||
| User User | The user ID or name of the person who executed the activity. | ||
| Description This attribute identifies the individual or system user responsible for a specific process step. It helps in understanding workload distribution, identifying training needs, and analyzing performance across different users or teams. In analysis, it can be used to filter the process map to see how specific users perform their tasks or to identify activities that are frequently handled by a small group of specialists. It can also highlight potential automation opportunities for repetitive, manual tasks. Why it matters Attributes user responsibility for process steps, enabling analysis of team performance, workload distribution, and adherence to procedures. Where to get Typically found in transaction logs as 'User Name', 'Changed By', or 'Created By' fields within Kinaxis RapidResponse. Examples JSMITHUSER123BATCH_SYSTEM | |||
| Forecasted Quantity ForecastedQuantity | The predicted demand quantity for a product generated during the forecasting phase. | ||
| Description This attribute contains the quantity of a product that was predicted to be ordered in a given period. It represents the output of the demand planning process. This data is essential for the Demand Forecast Accuracy dashboard and the Forecast-to-Actual Order Deviation KPI. By comparing this value with the actual 'Order Quantity', businesses can assess the reliability of their forecasts, which is critical for optimizing inventory levels and production planning. Why it matters Serves as the baseline for measuring forecast accuracy, helping to improve inventory management and reduce costs associated with overstocking or stock-outs. Where to get This data originates from the demand planning or forecasting modules within Kinaxis RapidResponse. Examples 120480030 | |||
| Is On-Time Delivery IsOnTimeDelivery | A calculated flag that indicates whether an order was delivered on or before the requested delivery date. | ||
| Description This boolean attribute is derived by comparing the 'Actual Delivery Date' to the 'Requested Delivery Date'. It simplifies performance analysis by categorizing every completed order as either on-time or late. This flag is the primary driver for the On-Time Delivery Performance dashboard and the On-Time Delivery Rate KPI. It allows for easy filtering, aggregation, and visualization of delivery performance across different dimensions like customer, product, or region. Why it matters Provides a clear, binary outcome for delivery performance, simplifying the calculation of on-time KPIs and enabling powerful dashboard visualizations. Where to get This attribute is not found in the source system but is calculated during the data transformation phase for process mining. Examples truefalse | |||
| Is Rework IsRework | A calculated flag that indicates if an activity is part of a rework loop, such as a repeated quality check or production step. | ||
| Description This boolean attribute identifies activities that occur as part of a rework cycle. It is typically flagged as 'true' when a production or quality control activity is repeated for the same Logistics Order after an initial attempt. This flag is essential for the Quality Control Rework Analysis dashboard and the Rework Rate KPI. It allows analysts to easily quantify the frequency of rework and isolate the process flows that are causing inefficiencies, increased costs, and longer cycle times. Why it matters Directly flags inefficient rework loops within the process, making it easy to quantify the impact of quality issues on cost and cycle time. Where to get This attribute is calculated within the process mining tool by detecting repeated sequences of activities for a given case. Examples truefalse | |||
| Mode of Transport ModeOfTransport | The method of transportation used for shipping the goods, such as truck, air, or sea. | ||
| Description This attribute specifies how goods are moved from one location to another. It can include standard and expedited options. It is key for the Expedited Order Overview dashboard and the Expedited Order Percentage KPI. Analyzing this attribute helps identify how often costly expedited shipping is used, which can indicate underlying issues in planning or execution. It also supports transportation leg time analysis by comparing the efficiency of different modes. Why it matters Identifies transportation methods, which is key to analyzing logistics costs, transit times, and the frequency of expensive expedited shipments. Where to get This information is typically stored in shipment or transportation documents within Kinaxis RapidResponse or an integrated TMS. Examples Air FreightOcean FCLTruckloadNext-Day Air | |||
| Order Fulfillment Cycle Time OrderFulfillmentCycleTime | The total time elapsed from when a customer order is received to when the final proof of delivery is signed. | ||
| Description This is a case-level metric that measures the end-to-end duration of the entire order fulfillment process. It is calculated by taking the timestamp of the last activity ('Proof Of Delivery Signed') and subtracting the timestamp of the first relevant activity ('Customer Order Received'). This metric is the cornerstone of the Order Fulfillment Cycle Time dashboard and the Avg Order-to-Delivery Cycle Time KPI. It provides a high-level view of the overall efficiency and speed of the supply chain, helping to track improvements and identify systemic delays over time. Why it matters Represents the total end-to-end duration of the fulfillment process, serving as a critical KPI for measuring overall supply chain speed and efficiency. Where to get This is not a field in the source system but is a metric calculated at the case level within the process mining software. Examples 10 days 4 hours25 days 12 hours15 days 2 hours | |||
| Order Quantity OrderQuantity | The quantity of a product ordered by the customer. | ||
| Description This attribute specifies the number of units of a particular product included in a customer order. It is a fundamental piece of transactional data. In analysis, order quantity is used to compare against forecasted quantities to measure forecast accuracy. It also helps in prioritizing high-volume orders and understanding the scale of production and logistics operations required for different orders. Why it matters Crucial for measuring demand forecast accuracy by comparing it to forecasted amounts and for understanding the volume drivers in the supply chain. Where to get This is a standard field in customer order line item data within Kinaxis RapidResponse. Examples 100500025 | |||
| Plant Plant | The manufacturing plant or facility where production or processing activities occur. | ||
| Description This attribute identifies the specific physical location, such as a factory or production site, involved in the supply chain process. It provides geographical and organizational context to production-related activities. Analyzing the process by plant allows for performance comparison across different sites. It can help identify which plants are more efficient, which have higher rework rates, and where production bottlenecks are most common, supporting resource utilization analysis. Why it matters Provides location context for production activities, enabling performance benchmarking and bottleneck analysis across different manufacturing sites. Where to get This is a common attribute in production, inventory, and logistics data within Kinaxis RapidResponse. Examples PLANT-01-DEPLANT-02-USPLANT-03-CN | |||
| Purchase Order Number PurchaseOrderNumber | The unique identifier for a purchase order issued to a supplier for raw materials or components. | ||
| Description This attribute is the key identifier for procurement activities. It links the request for materials ('Purchase Requisition Created') to the official order sent to a supplier ('Purchase Order Issued') and the subsequent receipt of those materials ('Raw Materials Received'). While the Logistics Order is the case ID, the Purchase Order Number is a critical business document reference that allows for drilling down into specific supplier transactions. It is essential for analyzing the Supplier Delivery Performance dashboard in detail. Why it matters Acts as a key reference for all procurement activities, enabling detailed analysis of the purchasing sub-process and supplier performance. Where to get This is a primary field in purchasing and procurement modules or workbooks within Kinaxis RapidResponse. Examples PO4500012345PO4500012346PO4500012347 | |||
| Rejection Reason RejectionReason | A code or text explaining why an item failed a quality control check. | ||
| Description This attribute captures the specific reason for a quality failure. It provides critical context when a 'Quality Control Passed' activity does not occur, and instead, the process loops back to production for rework. In the Quality Control Rework Analysis dashboard, this data provides the 'why' behind rework events. Analyzing rejection reasons helps to identify the root causes of quality problems, such as material defects, equipment malfunction, or operator error, enabling targeted improvement actions. Why it matters Provides crucial context for quality failures and rework loops, enabling root cause analysis to improve product quality and reduce waste. Where to get This information would be found in quality management modules or tables, linked to quality inspection events. Examples Dimension out of specSurface scratchIncorrect component | |||
| Resource Resource | The specific machine, production line, or equipment used to perform an activity. | ||
| Description This attribute identifies the physical resource involved in a process step, particularly in manufacturing. It could be a specific machine, an assembly line, or a packing station. Analyzing the process by resource is central to the Supply Chain Resource Utilization dashboard. It helps to understand the workload and performance of different resources, identify which machines are bottlenecks, and optimize resource allocation for better throughput and efficiency. Why it matters Identifies the specific equipment or line used, which is essential for analyzing resource utilization, capacity constraints, and production bottlenecks. Where to get This data is often found in manufacturing execution systems (MES) that integrate with Kinaxis, or within detailed production planning data. Examples ASSEMBLY-LINE-01CNC-MACHINE-05PACK-STATION-B | |||
| Supplier ID SupplierIdentifier | The unique identifier for the supplier providing raw materials or components. | ||
| Description This attribute identifies the supplier involved in procurement-related activities, such as 'Purchase Order Issued' and 'Raw Materials Received'. It is essential for the Supplier Delivery Performance dashboard, allowing the business to measure and compare the on-time performance and lead times of different suppliers. This analysis helps in supplier relationship management, identifying reliable partners, and mitigating risks in the inbound supply chain. Why it matters Enables performance analysis of suppliers, which is critical for identifying procurement bottlenecks and ensuring a reliable inbound supply chain. Where to get Located in purchasing documents and goods receipt records within Kinaxis RapidResponse, typically named 'Supplier ID' or 'Vendor Number'. Examples SUP-A100SUP-B200SUP-C300 | |||
| Warehouse Warehouse | The warehouse or distribution center from which goods are picked, packed, and shipped. | ||
| Description This attribute specifies the storage facility involved in fulfillment activities. It is key to understanding the logistics and inventory management parts of the supply chain. By analyzing activities per warehouse, businesses can compare the efficiency of their distribution network. This is useful for dashboards related to inventory bottlenecks and fulfillment throughput, helping to identify slow-moving inventory or inefficient warehouse operations. Why it matters Pinpoints the specific warehouse or distribution center, allowing for analysis of inventory movement, picking efficiency, and fulfillment speed by location. Where to get Found in inventory management and shipment data, often associated with goods picking and shipping events. Examples WH-EAST-01WH-WEST-03DC-CENTRAL | |||
Supply Chain Management Activities
| Activity | Description | ||
|---|---|---|---|
| Customer Order Received | Marks the official start of the logistics order lifecycle when a customer's sales order is created or ingested into the system. This is typically an explicit event captured from an integrated ERP or order management system. | ||
| Why it matters This is the primary start point for the case. It is essential for measuring the overall order-to-delivery cycle time and understanding order intake volumes. Where to get Kinaxis ingests sales order data from source ERP systems. This event is captured from the creation timestamp of the sales order record within the Kinaxis data model. Capture Timestamp of sales order creation, typically from an ERP integration. Event type explicit | |||
| Goods Shipped | This event occurs when the packed goods are loaded onto a transport vehicle and leave the warehouse or production facility. This marks the beginning of the in-transit leg of the journey. | ||
| Why it matters This is a key milestone for tracking on-time delivery performance and transportation leg times. It provides the 'actual ship date' for many KPI calculations. Where to get The timestamp is from the 'Post Goods Issue' transaction in an ERP or a 'Ship Confirm' transaction in a WMS/TMS, which is integrated with Kinaxis. Capture Timestamp from a goods issue or ship confirmation transaction. Event type explicit | |||
| Order Canceled | Represents the termination of a logistics order before fulfillment is complete. This is an explicit action that serves as a final, unsuccessful end state for the process. | ||
| Why it matters Tracking cancellations is important for understanding demand attrition and process failures. Analyzing the reasons for cancellation can reveal issues with product, pricing, or service. Where to get Captured from the timestamp when a cancellation status or reason code is applied to the sales order record, typically sourced from an ERP system. Capture Timestamp of the status change to 'Canceled' on the sales order. Event type explicit | |||
| Production Scheduled | Represents the point where the logistics order is officially slated for production with a defined date and resource allocation. This is a core planning output of Kinaxis RapidResponse. | ||
| Why it matters Marks the transition from planning to execution. Analyzing the time between this and actual production start can reveal scheduling inefficiencies or resource constraints. Where to get This is an explicit event captured from the timestamp when a production or manufacturing order is firmed and scheduled in the Kinaxis planning engine. Capture Timestamp when a planned order is converted to a firm production order. Event type explicit | |||
| Proof Of Delivery Signed | The final confirmation that the customer has received the goods in acceptable condition. This is a critical event that officially closes the logistics order. | ||
| Why it matters This is the definitive end point for the order-to-delivery cycle time KPI. It confirms successful fulfillment and is often a trigger for invoicing. Where to get This event is captured when proof of delivery documentation is received and the timestamp is entered, often manually or via a carrier integration, against the order. Capture Timestamp when the proof of delivery status is updated for the order. Event type explicit | |||
| Purchase Order Issued | A purchase order for required materials is sent to an external supplier. This is a critical milestone, representing a formal commitment and the start of the supplier lead time. | ||
| Why it matters This activity is key to measuring supplier delivery performance and identifying delays in the procurement phase that impact the entire supply chain. Where to get Kinaxis captures the creation or issue timestamp of the purchase order, which is often sourced from an integrated ERP system's procurement module. Capture The issue date timestamp on the purchase order record. Event type explicit | |||
| Demand Forecast Generated | This activity represents the creation or update of a demand forecast for a product, which serves as an initial signal for a potential logistics order. This event is typically captured when a new forecast is published within the Kinaxis RapidResponse planning engine. | ||
| Why it matters Analyzing the forecast provides a baseline for measuring forecast accuracy against actual orders, which is crucial for optimizing inventory levels and production planning. Where to get This event is explicitly logged in Kinaxis RapidResponse's demand planning module when a new forecast version is saved or published. It's associated with product and time period. Capture Logged when a new forecast is created or updated in the demand planning scenario. Event type explicit | |||
| Goods Delivered | Represents the arrival of the shipment at the customer's destination. This event is often captured from carrier data feeds integrated into a Transportation Management System (TMS) or Kinaxis. | ||
| Why it matters This activity marks the end of the transportation leg. Comparing this to the planned delivery date is crucial for measuring carrier performance and on-time delivery. Where to get The timestamp is received from carrier status updates, often via EDI or API, and is recorded against the shipment or delivery record in the system. Capture Timestamp from an electronic carrier status update indicating delivery. Event type explicit | |||
| Goods Picked and Packed | This activity marks the process of collecting the items for an order from the warehouse and preparing them for shipment. This data is typically captured from a Warehouse Management System (WMS). | ||
| Why it matters This is the start of the final fulfillment phase. Delays here can indicate warehouse inefficiencies, labor shortages, or poor inventory slotting. Where to get Captured from the completion timestamp of the picking and packing transaction in an integrated WMS, associated with the delivery or sales order. Capture Completion timestamp of the picking transaction from a WMS. Event type explicit | |||
| Goods Produced | This activity signifies that the manufacturing process for the finished goods is complete. This event is typically received from an integrated Manufacturing Execution System (MES) or ERP production module. | ||
| Why it matters Completing this activity is a critical milestone that ends the production lead time. It allows for the analysis of manufacturing cycle times and adherence to the schedule. Where to get The timestamp is captured from a production completion confirmation transaction in an MES or ERP system, which is then fed into Kinaxis. Capture Timestamp of the final production order confirmation. Event type explicit | |||
| Inventory Availability Checked | Represents the system checking for available inventory or calculating an available-to-promise (ATP) date for the order. This is a core planning function within Kinaxis and may be logged as a specific event or inferred from status changes. | ||
| Why it matters This activity helps identify bottlenecks caused by inventory shortages or slow allocation processes, which directly impact fulfillment speed and customer promises. Where to get This can be an explicit log from an ATP check execution or inferred from a status change on the order line, for example, from 'New' to 'Inventory Confirmed'. Capture Inferred from an order line status change related to inventory confirmation. Event type inferred | |||
| Order Block Applied | This event occurs when an order is halted for a specific reason, such as a credit check failure, engineering hold, or quality concern. This is typically inferred from a status change. | ||
| Why it matters Blocks are a primary source of process delays. Identifying when, why, and for how long blocks are applied is critical for uncovering bottlenecks and improving flow. Where to get Inferred from a status change on the sales order or order line indicating a block. The reason code associated with the status provides context. Capture Inferred from a status change to a 'Blocked' or 'Hold' state. Event type inferred | |||
| Purchase Requisition Created | This activity signifies the creation of an internal request to procure necessary raw materials or components for the logistics order. It is an explicit event that triggers the procurement sub-process. | ||
| Why it matters Tracking this helps connect the customer order fulfillment process with the procurement process, allowing for analysis of internal approval delays before a PO is issued. Where to get The creation timestamp of a purchase requisition record in the procurement or supply planning module, often linked to the originating sales order. Capture Creation timestamp of the purchase requisition record. Event type explicit | |||
| Quality Control Passed | Indicates that the produced goods have successfully passed all quality inspection criteria. This is often inferred from a status change on the production or inventory record. | ||
| Why it matters This activity serves as a critical quality gate. Failures or rework loops originating from this step highlight production quality issues and cause significant delays. Where to get Inferred from a status update on the inventory lot or batch, changing from 'Awaiting Inspection' to 'Released' or 'Unrestricted'. The timestamp of this change is used. Capture Inferred from a status change on the inventory batch record to 'Unrestricted Use'. Event type inferred | |||
| Raw Materials Received | This event marks the arrival and acceptance of raw materials from a supplier at the warehouse or production facility. The data is typically captured from an integrated WMS or ERP system. | ||
| Why it matters This activity concludes the supplier lead time measurement. Delays here have a direct downstream effect on production schedules and final delivery dates. Where to get Captured from a goods receipt transaction in an ERP or WMS, which includes a timestamp. This data is then integrated into the Kinaxis platform. Capture Timestamp of the goods receipt posting from a source system. Event type explicit | |||
Extraction Guides
Extraction methods for this process are currently being validated. Please check back later or contact us for assistance.