Connect981 – Content Dev

RSC Topic: Traceability & Genealogy

Lot, serial, and unit-level tracking from raw material through as-built record.

  • Material certification

    Material certification commonly refers to the formal documentation provided by a supplier or manufacturer that confirms a specific material, batch, or heat meets defined requirements. These requirements can include chemical composition, mechanical or physical properties, manufacturing process constraints, and applicable regulatory or industry standards.

    In industrial and regulated manufacturing, material certification is typically a controlled document that travels with raw materials, semi-finished goods, or purchased components. It is used to support traceability, quality assurance, and compliance with customer, internal, or regulatory specifications.

    What material certification usually includes

    Although formats vary by sector and standard, a material certificate commonly contains:

    • Identification of the material (grade, alloy, specification, description)
    • Supplier and manufacturer information
    • Batch, lot, heat, or melt number for traceability
    • Reference to applicable standards or specifications (for example, ASTM, EN, AMS, internal spec)
    • Test results and inspections performed (for example, chemical analysis, tensile properties, hardness)
    • Statement of conformity to the specified requirements
    • Date, sign-off, and sometimes digital or physical authorization

    Types and levels of material certificates

    Different industries and standards define specific material certificate types. Examples include:

    • Mill test report (MTR) or mill test certificate: Issued by the producing mill for metals, documenting chemistry and mechanical test results.
    • Certificate of Analysis (CoA): Common in chemicals, polymers, and pharmaceuticals, recording measured properties against defined limits.
    • Certificate of Conformance (CoC): A statement that the material complies with specified requirements, sometimes without detailed test data.

    The exact terminology and required content depend on sector-specific practices and referenced standards.

    Operational role in manufacturing systems

    Within manufacturing operations, material certifications are typically:

    • Captured during receiving and incoming inspection and linked to purchase orders and lots
    • Referenced in MES, ERP, PLM, or QMS records to support material traceability and genealogy
    • Reviewed by quality or engineering to confirm material suitability before release to production
    • Retained as part of device history records, batch records, or as-built documentation for audit and customer requirements

    In regulated environments, material certification data may be cross-referenced during nonconformance investigations, MRB decisions, and root cause analysis to verify that the supplied material met specified requirements.

    Scope and limitations

    Material certification typically:

    • Includes: Evidence of tests performed on the material, traceability identifiers, and declarations of conformity to specified requirements.
    • Does not by itself guarantee: Product-level performance, process capability, or overall system compliance. It is one element of a broader quality and traceability framework.

    Common confusion

    • Material certification vs. product certification: Material certification applies to the supplied material or component. Product certification refers to the finished product being assessed against product-level standards or regulations.
    • Certificate of Conformance vs. detailed test certificates: A CoC may only state that the material meets requirements, while a material test report or CoA includes specific measured values and test details.

    Relation to quality and traceability

    Material certifications are often controlled within document management and quality management systems. They support audit readiness, enable backward traceability from finished goods to originating material lots, and provide objective evidence that materials used in production were selected and released according to specified requirements.

  • part genealogy

    Part genealogy commonly refers to the complete, traceable history of how an individual part or serialized unit was produced, inspected, moved, and modified across its lifecycle. It captures the chain of materials, processes, equipment, people, and data that contributed to that specific part.

    What part genealogy includes

    In industrial and regulated manufacturing environments, part genealogy typically covers:

    • Material lineage: source lots, heat numbers, batches, and supplier details for raw materials and components used in the part.
    • Process history: operations performed (machining, coating, assembly, test, rework), the routing followed, and the sequence of steps.
    • Equipment and tools: key machines, test stands, fixtures, and calibrated gages involved at each operation.
    • Work instructions and revisions: which versions of travelers, work instructions, and specifications were in force when the part was processed.
    • Quality and inspection records: inspection results, measurements, test data, nonconformances, deviations, concessions, and approvals tied to the part.
    • Operator and timestamp data: who performed or approved each step and when it occurred.
    • Location and movement: WIP locations, transfers between work centers or sites, and shipping/receiving events for the part or its subcomponents.

    Part genealogy is often implemented through MES, ERP, PLM, or specialized traceability systems that link serial numbers, lot numbers, and work orders to detailed execution and quality data.

    How part genealogy is used operationally

    Operationally, part genealogy shows up as the ability to:

    • Open a specific serial number and see its as-built structure, including all child parts and material lots.
    • Trace from a supplier lot or process issue to all affected finished parts for containment or recall analysis.
    • Provide evidence of traceability during audits or customer reviews in regulated sectors like aerospace, defense, and medical devices.
    • Support root cause analysis by correlating defects with specific materials, equipment, process parameters, or work instructions used on the part.

    What part genealogy is not

    • It is not just a work order history; it must resolve down to individual serialized parts or clearly defined lots.
    • It is not only design data; CAD and engineering BOMs describe intended configuration, while genealogy records what was actually built and how.
    • It is not limited to a single system; in practice, genealogy often spans MES, ERP, QMS, and PLM data that must be linked coherently.

    Common confusion

    • Part genealogy vs. traceability: Traceability is the broader capability to track and link product, process, and data over time. Part genealogy is the specific, detailed trace for a part (or lot), usually presented as an as-built and as-processed record.
    • Part genealogy vs. product genealogy: In some organizations, “product genealogy” refers to the full build-up across multiple levels of assembly, while “part genealogy” focuses on a specific component or serialized item. In many contexts, the terms are used interchangeably.

  • product traceability

    Product traceability commonly refers to the ability to identify and follow a product, its components, and associated data through all stages of production, processing, distribution, and sometimes use and service. In industrial and regulated manufacturing environments, this includes linking materials, process steps, equipment, operators, test results, and quality decisions to specific product units or batches.

    What product traceability includes

    In practice, product traceability typically covers:

    • Identification: Unique identifiers such as serial numbers, lot numbers, batch IDs, or barcodes applied to materials, components, and finished goods.
    • Process history: Records of when, where, and how a product was manufactured, including work orders, process parameters, and equipment used.
    • Material genealogy: The relationships between raw materials, components, subassemblies, and final products.
    • Quality and test data: Inspection results, measurements, nonconformances, rework, and release decisions linked to specific units or lots.
    • Supply chain data: Supplier information, incoming inspection results, and shipment/receiving records.
    • Distribution records: Where each product unit or lot was shipped, installed, or used, often including customer or site information.

    Product traceability can be implemented at different levels of granularity, from batch-level (lot traceability) to unit-level (full serial traceability). In high-risk or highly regulated sectors, unit-level traceability is often required or expected.

    Operational meaning in manufacturing systems

    Operationally, product traceability relies on coordinated data capture across OT and IT systems. Typical enablers include:

    • MES and shop floor systems capturing work-in-process, routing, operator actions, and process data.
    • ERP and inventory systems recording material movements, batch/lot assignments, and shipments.
    • Quality systems (QMS, LIMS, SPC) storing inspection, test, and deviation data linked to product identifiers.
    • Labeling and identification technologies such as barcodes, QR codes, RFID, or nameplates.

    These systems together support end-to-end tracking, from raw material receipt through final shipment and, where relevant, field service or recall actions.

    Role in standards and regulated environments

    In regulated or safety-critical industries, product traceability is often a key expectation within quality management and compliance frameworks. It supports:

    • Defect and complaint investigation by enabling rapid identification of affected lots or serial numbers.
    • Targeted containment and recalls by tracing forward from suspect components to finished goods and customers.
    • Root cause analysis by providing linked histories of materials, processes, and test results.
    • Supplier and internal audit evidence by demonstrating how product records are connected and retrievable.

    Automotive quality standards, such as IATF 16949, commonly refer to product traceability expectations, especially where safety, regulatory, or customer-specific requirements apply.

    What product traceability is not

    Product traceability is related to, but distinct from, several nearby concepts:

    • It is not only a labeling activity. Labels provide identifiers, but traceability requires consistent capture and maintenance of linked records.
    • It is not the same as production scheduling. Scheduling defines when and where work should happen; traceability describes what actually happened and to which product units.
    • It is not limited to inbound and outbound tracking. Effective traceability spans intermediate process steps and in-process transformations.

    Common confusion

    Product traceability is closely related to:

    • Genealogy: Often used to describe the parent-child relationships of materials and components that make up a product. Genealogy is a core part of traceability.
    • Lot traceability: Traceability at batch or lot level instead of individual serial number. This is a subset of product traceability with coarser granularity.
    • Process traceability: Focused on tracking process conditions and steps. Product traceability typically combines both product and process perspectives.

    Link to the automotive quality context

    In automotive and similar long-lifecycle industries, product traceability is often addressed within quality management systems aligned with standards such as IATF 16949. Requirements typically include the ability to identify products and components, trace them back to manufacturing records and suppliers, and trace them forward to vehicles or assemblies in the field, especially where safety or regulatory characteristics are involved.

  • Purchase Order

    A Purchase Order (PO) is a formal commercial document issued by a buying organization to a supplier that authorizes the purchase of specified goods or services under defined terms and conditions. It is a key control instrument in procurement and financial processes, especially in industrial and regulated manufacturing environments.

    Core characteristics

    A Purchase Order typically includes:

    • Unique PO number for identification and traceability
    • Buyer and supplier information
    • Description of goods or services, including part numbers or SKUs
    • Quantities, prices, currency, and payment terms
    • Required delivery dates and delivery locations
    • Applicable quality, regulatory, or technical requirements
    • Reference to related contracts, quotes, or framework agreements

    In most organizations, Purchase Orders are created, approved, and maintained in an ERP, procurement, or financial system. They provide the commercial basis for receiving, inspection, and invoicing activities.

    Role in industrial and regulated environments

    In manufacturing and other industrial operations, a Purchase Order commonly serves to:

    • Control external spending by requiring authorization before purchase
    • Link incoming materials or services to cost centers, projects, or products
    • Support material traceability by associating received lots or serials with a PO number
    • Reference required specifications, certificates, or regulatory constraints for supplied items
    • Provide a contractual baseline for supplier performance and dispute handling

    On the shop floor, PO numbers are often used to identify which incoming materials, components, or outsourced services belong to a particular order, batch, or customer project. Inspection records, nonconformance reports, and supplier corrective actions may all reference the relevant PO.

    Interaction with other operational documents

    Purchase Orders are related to, but distinct from, several other common documents:

    • Work Orders (WO): A WO instructs internal or external resources to perform work (such as manufacturing, maintenance, or rework). A WO may depend on materials or services procured via one or more POs, but the WO governs execution, while the PO governs purchasing.
    • Production Orders / Manufacturing Orders: These define what to make, in what quantity, and by when. They may consume materials that were acquired under one or more POs.
    • Purchase Requisitions: Internal requests that precede approval and conversion into a formal PO.
    • Invoices: Supplier billing documents that typically reference a PO number for matching and approval.

    Common confusion

    Purchase Orders are commonly confused with:

    • Work Orders: A PO is a commercial agreement with a supplier. A WO is an instruction to perform work, often within MES, CMMS, or maintenance systems. They may reference each other but serve different control and traceability purposes.
    • Contracts: A PO may operate under an existing contract or framework agreement. The contract sets the broader legal relationship, while the PO specifies a particular transaction under that relationship.

    Context from the PO vs WO distinction

    In discussions that compare PO and WO, the Purchase Order represents the financial and commercial commitment recorded in ERP or procurement systems, while the Work Order represents operational work instructions in systems such as MES or CMMS. Understanding this separation helps maintain clear boundaries between purchasing control, production or maintenance execution, and compliance documentation.

  • Split Lot

    Meaning in manufacturing operations

    A **split lot** is a production lot that has been intentionally divided into two or more smaller units (sub-lots) after it has been created and identified as a single lot. Each resulting portion typically retains a traceable relationship to the original lot while acquiring its own lot or sub-lot identifier.

    Split lots are created so the separated portions can:

    – Follow different processing paths (e.g., different machines, routes, or recipes)
    – Be processed at different times or in different shifts
    – Undergo different tests, inspections, or dispositions
    – Be segregated due to quality, yield, or risk considerations

    In regulated or traceability-focused environments, the relationship between the original lot and all split lots is usually maintained in MES, LIMS, ERP, or other tracking systems.

    How split lots are used in workflows

    In typical production and quality workflows, split lots are used to:

    – **Manage capacity and scheduling**: Part of a lot is moved to another line or piece of equipment to reduce bottlenecks.
    – **Handle partial nonconformances**: A portion of a lot suspected of issues is split and placed on hold, while the remainder continues processing.
    – **Support experimentation or process changes**: One sub-lot may run with modified parameters while another follows the standard process, both still traceable back to the same source material.
    – **Enable staged release**: In some environments, a fraction of a lot may be tested and released earlier, while the rest awaits further processing or testing.

    Systems that support lot genealogy will record:

    – The parent lot ID
    – All child lot or sub-lot IDs
    – The split event (who, when, why, how much)

    This enables forward and backward traceability during investigations, recalls, or batch reviews.

    Boundaries and what it is not

    – A split lot **is not** a new and unrelated lot: it originates from, and is traceable to, a single parent lot.
    – It **does not imply** any specific quality status by itself; a split can be done for operational, capacity, or quality reasons.
    – It **is different from**:
    – **Lot merge**: combining multiple lots into one lot or batch.
    – **Lot resizing at creation**: initially creating smaller lots is not considered a split; a split occurs after a lot already exists as a single defined unit.

    Common confusion and related terms

    – **Lot split vs. partial disposition**: A split lot creates new traceable sub-lots. Simply scrapping or consuming a portion of a lot without establishing new identifiers is not typically recorded as a split.
    – **Split lot vs. sub-batch**: In some industries, “sub-batch” or “sub-lot” is used interchangeably with split lots, but the key distinction is the explicit derivation from a defined parent lot.

    Site context: OT, MES, and quality systems

    Within MES, ERP, and quality systems used in manufacturing:

    – Split lot functionality is commonly modeled as a transaction that adjusts inventory quantities and creates one or more new lot records linked to a parent.
    – Lot genealogy or traceability reports show the parent–child structure created by lot splits and merges.
    – In investigations and deviations, split lot history helps identify which portion of a parent lot was exposed to a given equipment, shift, or process condition.

    In regulated environments, documentation of lot split events (who performed the split, under what procedure, and how quantities balance) is often required to maintain robust material traceability and support audits or inspections.

  • characteristic ID

    A characteristic ID is a unique identifier assigned to a specific inspection or design characteristic so that it can be referenced consistently across drawings, inspection plans, CMM programs, quality records, and reporting forms.

    What a characteristic ID represents

    In regulated and industrial manufacturing, each measurable or verifiable requirement on a part or assembly (for example a dimension, geometric tolerance, surface finish, material property, or special process parameter) is treated as a separate characteristic. A characteristic ID:

    • Uniquely labels that requirement within a drawing, part number, or configuration
    • Links the requirement to inspection results, nonconformances, and approvals
    • Supports traceability when data moves between systems such as CMM software, MES, QMS, and reporting tools

    The ID can be numeric, alphanumeric, or follow a structured scheme (for example 001, 002A, 010.1). In many environments it is tied directly to balloon numbers applied on an engineering drawing.

    Use in AS9102 and FAI

    In aerospace first article inspection (FAI) and AS9102 workflows, the characteristic ID is commonly used to connect:

    • Ballooned drawing characteristics
    • Line items on AS9102 Form 3 (characteristic accountability)
    • CMM or other automated inspection results

    A stable, consistent characteristic ID scheme helps ensure that each result can be traced back to the exact requirement, even if data is transferred between different tools or suppliers.

    Operational considerations

    When characteristic IDs are used systematically, they typically:

    • Are assigned during drawing ballooning or inspection plan creation
    • Remain stable across revisions when possible, with clear rules for changes
    • Are stored in master data structures, such as characteristic libraries or digital inspection plans
    • Are referenced in CMM programs, manual inspection sheets, and electronic forms

    Characteristic IDs may also be used in SPC, capability analysis, and defect trend reporting to aggregate data for a given requirement over time.

    Common confusion

    • Characteristic ID vs. balloon number: In many shops the characteristic ID and the balloon number on the drawing are the same. In others, balloon numbers are visual labels, while the characteristic ID is a separate, system-assigned code. The important aspect is that there is a one-to-one and traceable mapping.
    • Characteristic ID vs. feature ID: A feature ID may describe a physical element of the part (for example hole H1), while the characteristic ID refers to a specific requirement on that feature (for example diameter, position, or surface finish). One feature can have multiple characteristics and therefore multiple IDs.

    Link to derived context

    In integrations between CMM software and AS9102 or other FAI tools, characteristic IDs act as the key that links measured values from the CMM to the correct line items on Form 3 or equivalent reports, enabling automated data import and consistent traceability.

  • What data should be captured inside a digital work instruction to support traceability?

    In a manufacturing or regulated operations environment, a digital work instruction should capture data that allows you to reconstruct who performed each step, what was used, how it was done, and what the result was. This supports product traceability, process genealogy, and audit readiness.

    Core identification and context data

    These fields link the work instruction execution to specific products, orders, and versions:

    • Work instruction identifier: instruction name or ID, revision level, and effective date.
    • Order and product identifiers: work order / job ID, part number, product family, configuration, batch/lot number, and serial numbers where applicable.
    • Process and operation context: operation or routing step ID, station or line, plant/site, and any shift or cell identifiers.

    Personnel and authorization data

    These fields show who did the work and who approved it:

    • Operator identity: user ID or badge ID for each person executing or contributing to a step.
    • Approver / verifier identity: supervisor, inspector, or quality approver tied to specific steps or the entire operation.
    • Electronic signatures: electronic acknowledgment that steps were completed or verified, as required by site procedures or regulations.

    Timing and execution data

    These fields support sequence reconstruction and cycle-time analysis:

    • Timestamps: start and end time for the instruction and, where needed, for individual steps.
    • Execution status: step-by-step status (e.g., completed, skipped per deviation, blocked) with reasons when not completed as planned.
    • Process duration: system-calculated durations or manually entered times if required for compliance or performance analysis.

    Materials, components, and consumables

    These fields tie the executed work to specific material units for genealogy:

    • Input materials: lot/batch numbers, serial numbers, or container IDs for all critical components, raw materials, and subassemblies consumed at each step.
    • Output units: resulting product serial numbers, lot/batch IDs, or container IDs.
    • Quantities and yields: planned vs actual quantities used and produced, with scrap and rework identified.

    Equipment, tools, and settings

    These fields connect product history to the assets and conditions used:

    • Equipment identifiers: machine, line, or station IDs and any key fixtures or tooling IDs.
    • Tooling and instruments: specific tool IDs, calibration-controlled instruments, and gauges used on critical steps.
    • Key parameters: setpoints, recipes, torque values, environmental conditions, or other critical process parameters when they are not already captured by connected equipment.

    Quality, inspection, and deviation data

    These fields show whether the work met requirements and what happened when it did not:

    • Inspection results: measured values, pass/fail checks, visual inspection outcomes, and signoffs for each required check.
    • Attachments and evidence: photos, test reports, or linked files showing completed work or test results.
    • Nonconformances: defect codes, descriptions of issues, and links to nonconformance or CAPA records.
    • Rework and repairs: records of rework instructions executed, including who performed them and which units were affected.

    Change control and linkage data

    These fields connect execution to controlled documents and upstream systems:

    • Document control links: references to controlled procedures, specifications, and drawings (IDs and revision levels).
    • System references: links to MES, ERP, LIMS, QMS, or PLM records associated with the job, material, or deviation.
    • Change rationale: notes or coded reasons when steps are performed differently from the base instruction under an approved deviation.

    Application in digital work instructions

    In practice, not every field is required for every operation. Sites typically define a standard data set for digital work instructions based on product risk, regulatory expectations, and integration with systems like MES and ERP. The key principle is that captured data must allow an auditor or investigator to reliably answer: which instruction and revision was followed, by whom, when, where, with which materials and equipment, under what conditions, and with what outcome.

  • flight-critical components

    Flight-critical components are aircraft or aerospace parts whose failure could directly affect the safe conduct of a flight, landing, or mission. They are typically subject to stringent design controls, manufacturing controls, inspection requirements, and traceability expectations because their performance is essential to maintaining vehicle safety and controllability.

    In industrial and regulated manufacturing environments, the term commonly applies to parts produced for commercial, military, or space flight systems, such as airframes, propulsion systems, control surfaces, landing gear, or critical fasteners and hardware. These components are often governed by specific customer requirements, aerospace standards, and regulatory oversight.

    Characteristics in manufacturing operations

    In a production context, flight-critical components typically involve:

    • Defined critical features such as dimensions, materials, and special processes that have direct impact on flight safety.
    • Elevated process control, including qualified equipment, validated processes, and controlled changes to methods and parameters.
    • Enhanced inspection and testing, for example higher sampling rates, 100% inspection, or nondestructive testing tied to documented acceptance criteria.
    • Robust traceability from raw material through each manufacturing step, often including operator, machine, and batch genealogy.
    • Formal nonconformance handling, including structured root cause analysis and controlled corrective and preventive actions when defects occur.

    Common confusion

    Flight-critical components are related to but distinct from several other terms:

    • Safety-critical components: A broader category that can include automotive, medical device, or industrial safety parts. Flight-critical is a specific subset focused on aviation and aerospace applications.
    • Mission-critical components: Parts whose failure may compromise mission objectives but not necessarily immediate flight safety. Flight-critical status usually implies direct impact on safe flight and landing, not only mission success.
    • Quality-critical or key characteristics: These refer to features or requirements that significantly affect form, fit, or function. Not all quality-critical features are flight-critical, although flight-critical components nearly always have defined key characteristics.

    Relevance to root cause and recurring scrap

    In environments that manufacture flight-critical components, recurring scrap or repeated nonconformances are treated with particular concern. Structured, evidence-based root cause analysis, disciplined change control, and verification of corrective actions are commonly expected controls to prevent the reappearance of defects that could affect flight safety. Manufacturing execution systems, quality systems, and document control processes often highlight flight-critical components as requiring higher rigor in data capture, review, and approval.