serialized parts

Core meaning

Serialized parts are individual units of a component, subassembly, or finished product that are each assigned a unique identifier (usually a serial number) and tracked as distinct items rather than as undifferentiated quantity.

In manufacturing and industrial operations, serialization allows each physical unit to be:

– Uniquely identified (e.g., serial number, data matrix code, RFID)
– Traced through specific process steps, equipment, and locations
– Associated with its own quality records, test results, and usage history
– Managed individually in inventory, logistics, and service systems

How serialized parts are used in manufacturing systems

In practice, serialized parts appear in multiple interconnected systems:

– **MES / shop-floor systems**: Track each serialized part as it moves through operations, work centers, and equipment. MES commonly stores:
– Operation history and timestamps
– Machine and tool identifiers
– Parametric and test data for each step
– Operator actions, rework, and nonconformances

– **ERP and inventory systems**: Track the same serial numbers at the order, inventory, and shipment level, including:
– Purchase or production orders that created the serial
– Stock location and status (e.g., available, blocked, scrapped)
– Customer shipment and delivery records

– **Quality and compliance systems**: Use serial numbers to link:
– Deviations, CAPAs, and nonconformance reports
– Inspection results and certificates
– Field complaints and returns (RMA) back to manufacturing records

Serialized parts and genealogy

Serialized parts are a core element of manufacturing genealogy and traceability:

– Each serialized part can be linked to the **batch, lot, or other serials** that went into it (component and material genealogy).
– The complete **as-built record** for a product can be reconstructed by following its serial through all recorded process steps and associated materials.
– In regulated industries, integration between MES and ERP is often required so that genealogy spans both production activities and downstream distribution.

Genealogy accuracy depends on consistent serialization rules, reliable data capture at each operation, and validated integration between systems, not on the label of any single system.

Boundaries and exclusions

Serialized parts **include**:

– Finished goods tracked individually (e.g., medical devices, aerospace components, high-value equipment)
– Critical components or subassemblies that require unit-level traceability
– Units where service history, maintenance, or recalls must be managed per item

Serialized parts **do not necessarily include**:

– **Lot- or batch-tracked items** that share a common identifier for a group of units instead of per-unit serials
– **Purely count-based inventory** (e.g., bulk commodities, fasteners) that are only tracked by quantity, not unique IDs

A material can be both serialized and lot-controlled, but serialization refers specifically to the **unit-level identity**.

Common confusion and related terms

– **Lot-controlled vs. serialized**: Lot control tracks a group of units under one lot/batch number; serialization tracks each physical unit separately, sometimes in addition to lot control.
– **Serial number vs. part number**: A part number identifies the type or design of an item; a serial number identifies a specific individual instance of that part.
– **Tracking by container vs. by unit**: Pallet or container IDs are not the same as serialized parts unless each contained unit also has and is managed by its own serial.

Site context: serialized parts in MES and ERP

Within the context of MES and ERP integration:

– **MES** typically tracks serialized parts at the **operation and equipment level**, capturing process history, parameters, and operator actions for each serial.
– **ERP** typically tracks the same serials at the **order, inventory, and shipment level**, reflecting commercial and logistical status.

Both perspectives describe the same serialized part, but at different levels of the manufacturing and business process. Consistent serialization and data exchange between these systems is essential for end-to-end traceability.