Your Production Planning Data Template

Universal process mining template
Your Production Planning Data Template

Your Production Planning Data Template

Universal process mining template

This is our generic process mining data template for Production Planning. Use our system-specific templates for more specific guidance.

Select a specific system
  • Standardized event log structure for consistent analysis.
  • Essential data fields and activities for comprehensive insights.
  • A flexible starting point for any Production Planning system.
New to event logs? Learn how to create a process mining event log.

Production Planning Attributes

This section outlines the recommended data fields and contextual information crucial for creating a comprehensive event log for your Production Planning process.
5 Required 7 Recommended 5 Optional
Name Description
Activity Name
ActivityName
The name of the specific business event or step that occurred within the production planning process.
Description

The Activity Name describes a specific task, status change, or event that happens during the lifecycle of a production order. These activities form the sequential steps of the process, such as 'Production Order Created', 'Materials Issued', or 'Production Completed'.

In process mining, activities are the nodes in the process map. Analyzing the sequence and frequency of these activities reveals the actual workflow, deviations from the standard process, and areas of rework or inefficiency. Different activities can be used to define milestones for KPI calculations, like measuring the time between 'Order Released' and 'Production Started'.

Why it matters

Activities define the steps of the process. Analyzing their sequence, duration, and frequency is the core of process mining.

Where to get

Activity names are often derived from system status changes, transaction codes, or event logs related to production order objects.

Examples
Production Order CreatedMaterial Availability CheckedOrder Released to Production
Event Time
EventTime
The precise timestamp, including date and time, indicating when a specific activity occurred.
Description

Event Time records the exact moment an activity took place. This timestamp is crucial for ordering events chronologically and for calculating durations between different steps in the process. It serves as the primary temporal data point for process analysis.

Accurate timestamps are the foundation for all time-based analysis in process mining. They are used to build the process map, calculate cycle times between activities, measure waiting times, and identify bottlenecks. For instance, the difference between the Event Time of 'Production Started' and 'Production Completed' provides the actual production duration for an order.

Why it matters

This timestamp is essential for ordering events chronologically and calculating all time-based metrics, such as cycle times and lead times.

Where to get

Timestamps are typically stored alongside transaction or status change records in the source system's event logs or document change history.

Examples
2023-10-26T09:00:00Z2023-10-26T14:30:15Z2023-10-27T08:45:00Z
Production Order ID
ProductionOrderId
The unique identifier for a production order, which represents a single case in the production planning process.
Description

The Production Order ID is the primary key that uniquely identifies a single manufacturing job or work order from its creation to its completion. It serves as the case identifier for process mining, linking all related activities, timestamps, and attributes together to form a complete end-to-end process view.

In analysis, this ID is fundamental for tracking the lifecycle of each production order. It allows analysts to trace the path of an order through various stages such as planning, material checking, release, execution, and closure. By grouping all events by the Production Order ID, it becomes possible to calculate case durations, identify common process variants, and pinpoint bottlenecks affecting specific orders.

Why it matters

This is the essential case identifier that connects all related events, making it possible to reconstruct and analyze the end-to-end production planning process.

Where to get

This identifier is typically found in the header table or primary document for production or work orders in the source system.

Examples
WO-2024-00123PRD000587121009845
Last Data Update
LastDataUpdate
The timestamp indicating when the data for this event was last refreshed or extracted from the source system.
Description

The Last Data Update timestamp marks the point in time when the data was last extracted from the source system. This is a technical attribute used to understand the freshness and timeliness of the data being analyzed.

This attribute is primarily used for data management and monitoring. It helps ensure that analyses are based on up-to-date information and allows data engineers to track the recency of the dataset. It is not typically used for direct process analysis but is critical for maintaining data integrity and trust in the results.

Why it matters

This technical field is vital for data governance, helping to track data freshness and ensure analyses are based on current information.

Where to get

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

Examples
2023-11-01T02:00:00Z2023-11-02T02:00:00Z2023-11-03T02:00:00Z
Source System
SourceSystem
Identifies the system of record from which the production planning data was extracted.
Description

The Source System attribute specifies the originating application or platform, such as an ERP or MES, where the event data was generated. In environments with multiple integrated systems, this field helps distinguish the origin of different process steps.

Understanding the source system is important for data validation, troubleshooting, and governance. It provides context for the data, as different systems may have unique ways of capturing and defining events. In a complex landscape, analyzing data from different source systems can reveal integration delays or process fragmentation between platforms.

Why it matters

Provides crucial context about data origin, which is essential for data governance and for analyzing processes that span multiple systems.

Where to get

This information may be available as a standard field in data extracts or can be added as a static value during the data transformation process.

Examples
SAP S/4HANAOracle Fusion CloudDynamics 365 F&O
Planned End Date
PlannedEndDate
The date and time when the production order is scheduled to be completed according to the production plan.
Description

The Planned End Date is the target timestamp for completing all production activities for an order. It represents the commitment date from production and is used to calculate the planned lead time.

Similar to the planned start date, this attribute is crucial for schedule adherence and on-time delivery performance analysis. Comparing the Planned End Date with the actual completion date reveals delivery variance and helps quantify the impact of production delays. Analyzing orders that frequently miss their planned end dates can highlight systemic issues in capacity planning, material supply, or production efficiency.

Why it matters

Acts as the key baseline for measuring on-time completion performance and understanding the drivers of production lead time variance.

Where to get

This is a standard planning date found in the production order header or scheduling details.

Examples
2023-11-12T17:00:00Z2023-11-20T17:00:00Z2023-12-05T17:00:00Z
Planned Quantity
PlannedQuantity
The target quantity of the product that is scheduled to be produced in the order.
Description

The Planned Quantity is the amount of the product that the production order is intended to yield. This value is set during the planning phase based on demand from sales orders, forecasts, or stock replenishment policies.

This attribute provides context to the scale of each production order. It can be used to analyze if larger or smaller orders are more prone to delays or quality issues. Furthermore, comparing the Planned Quantity to the final completed quantity helps in calculating yield rates, scrap rates, and production efficiency, which are key performance indicators for any manufacturing operation.

Why it matters

Provides the target production volume, which is essential for analyzing yield, scrap rates, and the impact of order size on process performance.

Where to get

The planned or target quantity is a fundamental field located in the header or item details of the production order.

Examples
100500025
Planned Start Date
PlannedStartDate
The date and time when the production order is scheduled to begin according to the production plan.
Description

The Planned Start Date is the target timestamp for commencing production activities for a given order. It is a key output of the scheduling process and serves as a baseline against which actual performance is measured.

This date is fundamental for schedule adherence analysis. By comparing the Planned Start Date with the actual start of production, companies can measure start-time variance and identify the root causes of delays. This analysis is critical for improving planning accuracy, managing shop floor capacity, and ensuring timely delivery to customers.

Why it matters

Serves as the baseline for measuring schedule adherence and analyzing the causes of delays between planning and execution.

Where to get

This is a standard planning date found in the production order header or scheduling details.

Examples
2023-11-10T08:00:00Z2023-11-15T08:00:00Z2023-12-01T08:00:00Z
Plant
Plant
The manufacturing facility, site, or location where the production order is being executed.
Description

The Plant attribute identifies the physical location where the production activities take place. It provides geographical or organizational context for the production order.

This attribute is crucial for comparative analysis between different manufacturing sites. By segmenting the process data by Plant, organizations can benchmark performance, identify best practices at high-performing locations, and uncover systemic issues at underperforming ones. It helps answer questions like, 'Which plant has the best schedule adherence?' or 'Are material availability issues concentrated in a specific location?'.

Why it matters

Enables performance benchmarking and comparison across different manufacturing locations, helping to identify site-specific issues and best practices.

Where to get

The plant or location is a fundamental attribute of a production order, typically defined at the order header level.

Examples
DallasFrankfurt Plant 1Shanghai
Product ID
ProductId
The unique identifier for the material, part, or product being manufactured in the production order.
Description

The Product ID specifies the item that is the target of the production order. This could be a finished good, a sub-assembly, or a component. It links the production planning process to the specific material being produced.

Analyzing the process by Product ID is essential for understanding product-specific variations. It can help identify if certain products have longer lead times, require more rework, or follow different production paths. This type of analysis enables targeted improvements, such as optimizing the planning process for high-volume products or addressing issues with complex, low-volume items.

Why it matters

Allows for filtering and comparing process performance across different products, revealing product-specific bottlenecks or inefficiencies.

Where to get

This identifier is a key piece of information on the production order and is typically found in the order header or item details.

Examples
FG-1001SA-205B800-0198-02
Production Order Status
ProductionOrderStatus
Indicates the current or final lifecycle status of the production order at the time of the event.
Description

The Production Order Status reflects the state of the order within its lifecycle, such as 'Created', 'Released', 'In Progress', 'Completed', or 'Cancelled'. This status provides a snapshot of where the order is in the overall process.

This attribute is highly valuable for root cause analysis. By filtering for orders with a 'Cancelled' status, analysts can investigate the reasons for cancellation. Comparing the process flow of orders that were completed on time versus those that were delayed can reveal patterns related to status changes. It also helps in identifying orders that get stuck in a particular status for too long.

Why it matters

Provides critical context about the order's lifecycle stage, which is essential for analyzing process deviations, delays, and outcomes like cancellations.

Where to get

This is a standard field on the production order header that is updated as the order progresses through its lifecycle.

Examples
CreatedReleasedTechnically CompletedClosed
User ID
UserId
The identifier of the user, planner, or employee responsible for performing a specific activity.
Description

The User ID identifies the person or, in some cases, the system user, who executed a particular step in the process. This could be the planner who created the order, the manager who approved it, or the supervisor who confirmed a production step.

Analyzing the process by User ID can help in understanding workload distribution, identifying training needs, and ensuring compliance. For instance, it can reveal if certain planners consistently create orders that require frequent adjustments or if approval steps are frequently delayed by specific individuals. This human-centric analysis provides valuable insights for performance management and resource optimization.

Why it matters

Attributes process activities to specific individuals, enabling analysis of user performance, workload, and adherence to procedures.

Where to get

User information is often recorded in the change logs or transaction history for production order events, linking a user to a specific timestamp and action.

Examples
JSMITHPLANNER_GROUP_A7001432
Completed Quantity
CompletedQuantity
The actual quantity of the product that was successfully produced and reported as finished for the order.
Description

The Completed Quantity represents the final, confirmed amount of goods produced by the order that meets quality standards. This is the actual output of the manufacturing process.

This attribute is critical for performance measurement. By comparing it against the Planned Quantity, analysts can calculate key metrics like order fulfillment rate, yield, and scrap. Analyzing discrepancies between planned and completed quantities can uncover issues related to production quality, machine performance, or material problems. It is a direct measure of the effectiveness of the production process.

Why it matters

Measures the actual output of the production process, enabling the calculation of critical KPIs like yield, scrap, and fulfillment rates.

Where to get

This value is derived from goods receipt transactions or production confirmations that record the quantity of finished goods from the order.

Examples
100495024
End Time
EndTime
The precise timestamp indicating when an activity or event was completed.
Description

The End Time represents the completion timestamp of an activity. While many activities are instantaneous and only have a Start Time, some have a measurable duration. For these activities, the End Time marks their conclusion.

When available, the End Time allows for a more precise analysis of activity durations. This is particularly useful for long-running tasks like 'Quality Inspection' or a specific production operation. By calculating the difference between End Time and Start Time, analysts can measure the exact processing time of individual steps, separating it from the waiting time between steps.

Why it matters

Enables the precise calculation of activity durations for tasks that are not instantaneous, helping to distinguish processing time from waiting time.

Where to get

This is often available for activities that have distinct start and stop events logged in the system, such as production confirmations or inspection records.

Examples
2023-10-26T11:05:00Z2023-10-26T17:20:45Z2023-10-28T10:00:00Z
Material Availability Status
MaterialAvailabilityStatus
Indicates whether all required materials and components for the production order are available.
Description

The Material Availability Status is a flag or indicator that signals whether the necessary raw materials and components are physically available to start production. This check is a critical step before releasing an order to the shop floor.

This attribute is key to analyzing the impact of material shortages on production schedules. By correlating material unavailability with delays in order release or production start, organizations can quantify the cost of poor material planning. This analysis can drive improvements in inventory management, procurement processes, and supplier collaboration to ensure materials are available when needed, preventing costly disruptions on the production line.

Why it matters

Directly measures the impact of material shortages on production delays, helping to identify and address issues in procurement and inventory management.

Where to get

This status is often the result of a material availability check transaction or batch job that runs against production orders before their release.

Examples
AvailableNot AvailablePartially Available
Production Order Type
ProductionOrderType
A classification that defines the purpose of the production order, such as standard, rework, or prototype.
Description

The Production Order Type categorizes orders based on their business purpose. Common types include standard production to fulfill regular demand, rework orders to fix defective items, prototype orders for new product development, or special orders for custom requests.

Analyzing the process by order type is extremely insightful. It allows for comparing the process flows and performance of different types of work. For example, rework orders are expected to follow a different path and have different cycle times than standard orders. Understanding the volume and process efficiency of each order type helps in resource planning and process optimization efforts tailored to specific business needs.

Why it matters

Allows for segmenting analysis by the order's business purpose, revealing different process behaviors for standard, rework, or special orders.

Where to get

This is a configuration field on the production order, often selected at the time of order creation to control how it is processed.

Examples
StandardReworkPrototype
Work Center
WorkCenter
The specific machine, production line, or area where a manufacturing operation is scheduled to take place.
Description

The Work Center identifies the specific resource, such as a machine, assembly line, or group of employees, responsible for carrying out a production step. A production order may pass through multiple work centers during its lifecycle.

This attribute enables a detailed, resource-level analysis of the production process. By analyzing the data by Work Center, companies can measure resource utilization, identify capacity bottlenecks, and compare the performance of similar machines or lines. It helps answer critical questions like, 'Which work center is the primary bottleneck?' or 'Is there a high rework rate associated with a specific machine?'.

Why it matters

Enables resource-level analysis to identify capacity bottlenecks, measure utilization, and track the performance of specific machines or production lines.

Where to get

Work center information is typically found at the operation or routing level of the production order.

Examples
CNC-05ASSEMBLY_LINE_2PACKING-A
Required Recommended Optional

Production Planning Activities

This section details the key process steps and significant milestones recommended for capturing to enable accurate process discovery and analysis.
7 Recommended 8 Optional
Activity Description
Goods Received From Production
This event records the receipt of the finished product from the production line into inventory. It formally increases the stock level of the produced material, making it available for sale or further use.
Why it matters

This is the final step that makes the product available to the business. The time between 'Production Completed' and this event shows any delays in moving goods from the shop floor to the warehouse.

Where to get

Captured from goods movement or inventory transaction logs, specifically looking for a receipt transaction type linked to the production order.

Capture

Use the posting date and time from material movement records where the movement type indicates a goods receipt from an order.

Event type explicit
Order Cancelled
Represents the cancellation of a production order before its completion. This is an alternative, unsuccessful end state for the process, stopping all further work on the order.
Why it matters

Tracking cancellations is critical for understanding demand volatility, planning accuracy, and process waste. It is a key exception path that requires investigation.

Where to get

Usually captured by a specific status change on the order, such as 'Cancelled' or the setting of a deletion flag.

Capture

Identify the timestamp when the order status is set to 'Cancelled' or a similar terminal, non-successful state.

Event type explicit
Order Closed
The final administrative and financial closing of the production order. At this stage, all costs are settled, variances are calculated, and the order is locked from further logistical or financial transactions.
Why it matters

This activity marks the definitive end of the order's lifecycle. Analyzing the time from 'Production Completed' to 'Order Closed' reveals the efficiency of the financial closing and reconciliation process.

Where to get

This is an explicit action, often performed by finance or controlling, that sets a final 'Closed' or 'Settled' status on the order.

Capture

Capture the timestamp associated with the final status change to 'Closed', 'Technically Completed', or 'Settled' in the order's status log.

Event type explicit
Order Released to Production
A critical milestone where the production order is formally released to the shop floor, authorizing the start of manufacturing activities. This action makes the order visible and actionable to production staff.
Why it matters

This marks the end of the planning phase and the beginning of the execution phase. The time between creation and release is a key measure of planning cycle time.

Where to get

This is almost always an explicit user or system action that changes the order's primary status to 'Released'.

Capture

Capture the timestamp associated with the status change to 'Released' from the order's status management log.

Event type explicit
Production Completed
This activity signifies that all manufacturing operations for the production order are finished on the shop floor. It is typically marked by the final confirmation against the last operation in the routing.
Why it matters

This marks the end of the physical production process. The time from 'Production Started' to this event is the pure manufacturing cycle time.

Where to get

Captured from the timestamp of the final confirmation entry for the last operation, or when the order status is updated to 'Finished' or 'Completed'.

Capture

Identify the latest timestamp from all production confirmation records for the order, or a specific status change event.

Event type explicit
Production Order Created
This activity marks the formal creation of a production order, which is the primary instruction to manufacture a specific quantity of an item. It serves as the starting point for the entire production process and establishes the unique case identifier.
Why it matters

This is the trigger event for the process. Analyzing the time from creation to other milestones helps measure overall planning efficiency and lead time.

Where to get

This event is captured when a new production order record is saved in the manufacturing or ERP system, often associated with an initial 'Created' status.

Capture

Look for the creation timestamp on the main production order header table or a specific status log entry indicating creation.

Event type explicit
Production Started
This activity marks the beginning of the first physical manufacturing operation for the order on the shop floor. It signifies the transition from staging to active production.
Why it matters

This is the true start of the production lead time. Analyzing the time from 'Order Released' to 'Production Started' highlights any delays in shop floor execution.

Where to get

Typically captured when an operator starts a job at a terminal or when the first time confirmation for an operation is recorded against the order.

Capture

Identify the earliest timestamp from all production confirmation or shop floor control records associated with the order.

Event type explicit
Material Availability Checked
Represents the verification that all necessary raw materials and components for the production order are available in inventory. This check confirms that production can proceed without material-related delays.
Why it matters

Failures or delays at this stage are a primary cause of schedule disruptions. Tracking this activity helps identify material planning issues and their impact on lead times.

Where to get

This is often an automated or manual action that results in a status update or a log entry on the production order.

Capture

Capture the timestamp when the material availability check is executed or when a corresponding status, like 'materials committed', is set.

Event type explicit
Materials Issued to Order
Represents the physical and transactional withdrawal of component materials from inventory for use in the production order. This confirms that the necessary raw materials have been moved to the production area.
Why it matters

This activity confirms material readiness for production. Delays between order release and material issuance can indicate warehouse or logistics inefficiencies.

Where to get

Captured from material transaction tables or goods movement logs linked to the specific production order number.

Capture

Use the posting date and time from material movement or inventory transaction records where the movement type indicates a goods issue to an order.

Event type explicit
Operation Completed
Represents the completion of an individual manufacturing step or operation within the production order's routing. A typical production order will have multiple 'Operation Completed' events.
Why it matters

Tracking individual operation completions allows for detailed analysis of the production flow, helping to identify bottlenecks and measure cycle time for specific manufacturing steps.

Where to get

Captured from shop floor data collection systems or time confirmation records for each operation listed in the order's routing.

Capture

Extract all confirmation events from operation-level tables, using the operation ID to distinguish between steps.

Event type explicit
Plan Adjusted During Production
This event signifies that a significant change was made to the production order after it was released to the shop floor. Common changes include adjustments to quantity, dates, routing, or the bill of materials.
Why it matters

Frequent adjustments indicate process instability and can lead to inefficiencies and increased costs. Identifying these events helps pinpoint the root causes of production plan changes.

Where to get

Usually inferred by analyzing change logs or audit trail tables that record modifications to key fields on the production order header or components list.

Capture

Compare snapshots of the order data or use change document tables to identify modifications made after the 'Order Released' event.

Event type inferred
Production Plan Approved
Signifies that the production plan and schedule have been reviewed and formally approved by a manager or planner. This approval is often a prerequisite for releasing the order to the shop floor.
Why it matters

Analyzing the time taken for approval reveals potential bottlenecks in the planning and review cycle. It separates the planning phase from the release-to-execution phase.

Where to get

Usually captured as an explicit approval action or a status change on the production order, for example from 'In Review' to 'Approved'.

Capture

Look for an approval timestamp or a status change event in the order's change log or status history.

Event type explicit
Production Plan Scheduled
This activity involves assigning the production order's operations to specific work centers and time slots. It considers resource capacity and material availability to create a detailed execution schedule.
Why it matters

This step determines the planned start and end dates. Comparing the scheduled dates to actual dates is crucial for measuring schedule adherence and identifying capacity bottlenecks.

Where to get

Typically recorded when a scheduling job is run for the order or when a planner manually saves the schedule, updating the planned operation dates.

Capture

Identify the event when scheduling-related fields, such as planned operation start and end times, are populated or updated.

Event type explicit
Quality Inspection Completed
Represents the completion and validation of a quality inspection. This event confirms whether the produced items meet the required standards and are cleared for the next step.
Why it matters

This is a key gate in the process. Failures or long delays in inspection can halt the entire production-to-inventory flow and are important to monitor.

Where to get

Recorded when a user makes a usage decision on a quality order or inspection lot, resulting in a status change like 'Accepted' or 'Rejected'.

Capture

Capture the timestamp when the final usage decision is recorded for the quality object associated with the production order.

Event type explicit
Quality Inspection Started
Indicates that a quality inspection process has been initiated for the materials produced by the order. This often involves creating a separate quality order or inspection lot linked to the production order.
Why it matters

This marks the beginning of the quality assurance cycle. The duration of this cycle can significantly impact the overall time it takes for a product to become available.

Where to get

Captured from the creation timestamp of a quality order or inspection lot record that references the production order.

Capture

Look for the creation event of related quality management objects in the system's quality module.

Event type explicit
Recommended Optional

Extraction Guides

How to get your data for process mining.

Extraction methods vary by system. For detailed instructions,

read our ETL guide

or select a specific process and system.