Connect981 – Content Dev

RSC Cluster: QMS Integration and Evidence Trails

The QMS Integration and Evidence Trails Cluster explains how execution workflows should align with quality management systems without attempting to replace them. It defines clear system boundaries and shows how operational activity produces governed quality records and audit evidence. The content emphasizes traceability, approvals, and record integrity rather than software overlap. This cluster helps teams integrate execution and quality without duplicating effort or creating confusion.

  • Net-Inspect

    Net-Inspect commonly refers to a cloud-based quality and supplier collaboration platform widely used in the aerospace and defense industry to exchange inspection and production data between OEMs and their suppliers.

    What Net-Inspect is in an aerospace context

    In regulated aerospace manufacturing, Net-Inspect is typically used as a secure, web-based portal where suppliers upload and manage product quality records requested by customers. These records often include:

    • AS9102 first article inspection (FAI) reports and supporting data
    • In-process and final inspection results
    • Certificates of conformance and related documents
    • Nonconformance information when required by customer process

    Prime manufacturers and Tier 1s may configure Net-Inspect to standardize how suppliers submit data, route it for review, and maintain an accessible history of inspection evidence.

    How it shows up in operations

    On the shop floor and in quality departments, Net-Inspect typically appears as a required step in fulfilling customer contract requirements. Common operational uses include:

    • Entering dimensional and characteristic results for FAI and production lots into customer-defined forms
    • Uploading ballooned drawings, material certs, and test reports to accompany AS9102 forms
    • Responding to customer feedback or rejection of submitted inspection packages
    • Maintaining a record of submitted FAIs linked to part numbers, revisions, and purchase orders

    Organizations often need to align internal systems (such as MES, ERP, or internal FAI tools) with Net-Inspect so that data can be transferred consistently and with minimal re-entry.

    Scope and boundaries

    Net-Inspect, in this sense, is:

    • A specific commercial software platform and portal used primarily for aerospace quality and supplier data exchange
    • Focused on documentation and evidence of quality and compliance rather than full production scheduling or shop-floor control

    It is not, by itself:

    • A complete enterprise resource planning (ERP) system
    • A full manufacturing execution system (MES) for routing, dispatching, and real-time work-in-process control
    • A general-purpose document management system for all internal quality records

    Common confusion

    Net-Inspect is sometimes informally used as a shorthand for the entire FAI process, especially in organizations where a specific customer mandates Net-Inspect submissions. It is more accurate to treat Net-Inspect as one possible system or portal used to submit AS9102/FAI data, not as the FAI process itself. The process requirements still come from standards (such as AS9102) and customer contracts, regardless of which portal or tool is used.

    Link to AS9102 and FAI workflows

    In many aerospace programs, Net-Inspect is the primary mechanism for submitting AS9102 first article inspection packages to customers. Suppliers may:

    • Create or import Form 1, Form 2, and Form 3 data into Net-Inspect
    • Attach supporting evidence like ballooned drawings and certificates
    • Track approval or rejection of FAIs within the portal

    Organizations often design their internal FAI workflows so that data originates in internal systems (spreadsheets, FAI software, or MES) and is then transferred or re-keyed into Net-Inspect to satisfy customer-specific submission requirements.

  • How do you prove characteristic accountability during an audit?

    Proving characteristic accountability means demonstrating that every required characteristic from a drawing or specification is traced to a specific operation, inspection, and result, with no gaps. Auditors are looking for evidence that you know where each characteristic is made, where it is verified, and how nonconformities are handled, under effective document control.

    1. Start from the source: requirements and ballooning

    Most audits begin with the design or customer requirement:

    • Current, approved drawing or specification under document control.
    • Ballooned drawing or characteristics map (for FAI/AS9102 and similar contexts).
    • Characteristic list (CL) or index linking each balloon/ID to a requirement (dimension, note, spec, KPC/CTQ, etc.).

    To prove accountability, you must show that every characteristic on that list is accounted for in your routing, work instructions, or inspection plan. Any missing or ambiguous mapping is a typical audit finding.

    2. Map each characteristic to an operation and method

    The next expectation is a clear link from characteristic to process step:

    • Routing or traveler that lists operations where the characteristic is created or affected (e.g., machining, heat treat, coating, assembly).
    • Work instructions or control plans identifying how the characteristic is produced and controlled (e.g., tooling, fixturing, SPC, special process controls).
    • Inspection plan that shows how and where each characteristic is verified (100% vs sample, in-process vs final, gage type, method).

    For an auditor, characteristic accountability is often tested by picking a balloon number at random and asking you to show, without gaps:

    • Where in the routing it is made/affected.
    • Which work instruction step or control addresses it.
    • Where the inspection or verification is planned and recorded.

    3. Provide objective evidence: inspection and test records

    Traceability requires objective records, not just plans. Typical evidence includes:

    • FAI forms (e.g., AS9102 Form 3), linked to ballooned characteristics.
    • In-process and final inspection reports tied to specific operations.
    • Electronic inspection data (CMM output, SPC charts) with clear characteristic IDs.
    • Gage IDs, calibration status, and operator signoffs for each measurement step.

    To prove accountability, the record must allow you to answer, for any characteristic:

    • Who inspected it (or what system did the check).
    • When it was checked (lot, work order, date/time).
    • What the result was (pass/fail, measured value).
    • What happened when it did not meet requirements (NCR/MRB, disposition, rework).

    4. Show nonconformance and disposition linkage

    Auditors will also test accountability with defects:

    • Nonconformance records that reference the characteristic ID, drawing balloon, or requirement.
    • MRB and disposition records (use-as-is, repair, scrap, rework) tied to the specific work order / serials.
    • Evidence that re-inspection or validation occurred after rework/repair.

    If you cannot map a nonconformance back to a specific characteristic and forward to the affected units, your characteristic accountability will be considered weak.

    5. Maintain configuration control and revision traceability

    In regulated and aerospace environments, auditors also expect you to prove which requirements applied at the time of manufacture:

    • Document control showing which drawing/spec revision was active for each lot or serial number.
    • Change control records for when characteristics were added, removed, or reclassified (e.g., KPC, safety-critical).
    • Updated ballooning and characteristic lists when the design or spec changes.

    Without configuration control, you might have good inspection records that no longer match the current drawing, which undermines your evidence during an audit.

    6. Digital vs paper: brownfield system realities

    Most plants have mixed systems: ERP, MES, PLM, QMS, plus spreadsheets and paper. Auditors will care less about whether it is digital or paper and more about whether the links are:

    • Complete: no orphan characteristics with no assigned control or inspection.
    • Consistent: IDs match between drawing, plans, and records.
    • Traceable: they can follow a characteristic from requirement to result quickly.
    • Controlled: revisions and changes are documented and approved.

    If you use multiple systems (common in brownfield environments), you will need a clear integration or at least a documented cross-reference to show, for example:

    • Drawing/balloon numbers from PLM linked to operation and inspection steps in MES/ERP.
    • Inspection results in an SPC or CMM system mapped back to the same characteristic IDs.
    • NCR records in QMS referencing the same characteristic codes and work orders.

    Full system replacement purely to improve characteristic accountability is rarely practical in aerospace-grade contexts due to validation effort, qualification, integration risk, and downtime. Incremental improvements (e.g., a digital inspection layer or better characteristic mapping tools) are usually more realistic and auditable if implemented under change control.

    7. Common audit failure modes for characteristic accountability

    Typical gaps that auditors flag include:

    • Characteristics on the drawing that are missing from control/inspection plans.
    • Balloon numbers that do not match between the drawing, FAI, and inspection sheets.
    • Special / safety-critical / key characteristics not clearly identified or treated differently.
    • Inspection records that show generic feature descriptions without a clear link to the characteristic ID.
    • Reworked characteristics without evidence of re-inspection and acceptance.
    • No evidence of which revision of the drawing/spec was used for a given batch.

    8. Practical steps to strengthen your evidence before an audit

    To improve your ability to prove characteristic accountability:

    • Perform an internal review where you pick random characteristics and walk the full chain: drawing → characteristic list → routing/operation → work instruction → inspection plan → inspection record → NCR (if any).
    • Standardize characteristic IDs and ensure they are used consistently across all systems.
    • Ensure FAI/AS9102 packages are complete, with clear balloon-to-result mapping, and kept accessible.
    • Close gaps where certain notes, surface finishes, or specification references are not explicitly inspected or controlled.
    • Put changes under formal change control, including updates to ballooning, CLs, travelers, and inspection plans.

    The goal is that, when an auditor points to any characteristic, you can show a clear, documented, and controlled path from requirement to evidence without scrambling across multiple systems or relying on tribal knowledge.

  • Specification

    A specification is a documented set of requirements that defines how a product, material, system, or process must perform or be executed. In industrial and manufacturing environments, specifications commonly describe technical parameters, materials, dimensions, tolerances, process steps, test methods, and acceptance criteria that must be met.

    Specifications can apply to many areas, including product design, raw materials, equipment settings, cleanliness levels, packaging, labeling, data formats, and software behavior. They are typically controlled documents and form part of the basis for design, manufacturing, inspection, and release decisions.

    How specifications are used in operations

    In regulated industrial environments, specifications often:

    • Define required characteristics for parts, assemblies, and finished goods (for example, dimensions, materials, performance limits).
    • Describe process requirements, such as machine parameters, environmental conditions, and sequence of operations.
    • Set quality and test requirements, including sampling plans, test methods, and pass/fail criteria.
    • Govern data and documentation, such as formats for electronic records or required fields in batch records.
    • Support integration across systems such as MES, ERP, and LIMS by standardizing identifiers and data attributes.

    Specifications are usually linked to related documents like drawings, work instructions, standard operating procedures (SOPs), and material master records. In many plants, non-conformances are recorded whenever there is a departure from an approved specification.

    Common types of specifications in manufacturing

    • Product or part specification: Defines what a product or component must be, including physical, chemical, and functional requirements.
    • Material specification: Defines requirements for raw materials, intermediates, and consumables, often including supplier and inspection criteria.
    • Process specification: Defines how a process must be carried out, including equipment settings, sequences, and critical process parameters.
    • Test or inspection specification: Defines how to verify requirements, including methods, instruments, sample sizes, and acceptance limits.
    • Interface or data specification: Defines how systems or components communicate, including data structures, formats, and protocols.

    Specification and compliance

    In regulated sectors, specifications are typically under document control and version governance. Changes often require formal review, approval, impact assessment, and sometimes revalidation. Manufacturing execution systems, quality systems, and ERP platforms frequently reference specification identifiers to ensure that the current, approved version is applied in planning, production, and release decisions.

    Common confusion

    • Specification vs. standard: A standard is a broader, often externally published reference document. A specification is usually a concrete, organization-specific or product-specific set of requirements that may be based on one or more standards.
    • Specification vs. work instruction: A specification defines what requirements must be met. A work instruction typically explains how operators should perform tasks to meet those requirements.
    • Specification vs. drawing: A drawing may visually represent geometry and some requirements, while a specification usually provides a structured, often text-based definition of requirements. In many organizations the drawing and specification together form the complete requirement set.

    Link to non-conformance management

    Non-conformances in the workplace are often defined as any departure from an approved specification, requirement, procedure, or standard. Effective specification management supports traceability, investigation, and remediation when parts, processes, systems, or documentation do not meet approved specifications.

  • revision history

    Revision history is the controlled record of changes made to a document, specification, software component, or system configuration over time. It typically shows what changed, when it changed, who authorized or performed the change, and why the change was made.

    In industrial and regulated manufacturing environments, a revision history is usually maintained for controlled documents such as work instructions, SOPs, batch records, quality procedures, drawings, and validated software configurations. It supports traceability, impact analysis, and audit evidence for how controlled information has evolved.

    Typical contents of a revision history

    A revision history section or log commonly includes:

    • Revision identifier (version number, letter, or code)
    • Effective date or release date for the revision
    • Brief description or summary of the change
    • Name or role of the author and/or approver
    • Reference to change request, deviation, CAPA, or ticket, if applicable
    • Status (draft, released, obsolete), depending on the system

    The revision history may be visible on the document itself (for example, on the first or last page) or stored in an electronic document management or MES/PLM system and accessed via metadata or audit trails.

    Operational role in manufacturing systems

    From an operational perspective, revision history is used to:

    • Demonstrate that current work instructions, recipes, or configurations are under change control
    • Support investigations by showing exactly what instructions or specifications were in effect at a given time or for a given lot
    • Help engineering, quality, and operations staff understand the rationale for previous changes and avoid unintended reversals
    • Align versions across integrated systems (for example, ensuring MES work instructions match ERP or PLM revisions)

    In digital systems, the revision history may be linked to electronic signatures, workflows, and automated audit trails. In paper-based or hybrid environments, it may be maintained manually as a controlled log.

    Common confusion

    • Revision history vs. version number: A version or revision number identifies a specific state. The revision history is the chronological record of all such states and their associated changes.
    • Revision history vs. audit trail: An audit trail is a detailed, system-level log of actions and events (such as view, modify, approve). The revision history is usually a higher-level summary of released changes, intended for human review.

    Relation to work instructions

    For manufacturing work instructions, the revision history shows how the instructions have been updated over time, such as changes to steps, parameters, tools, safety notes, or inspection criteria. This helps ensure operators use the correct, current revision and allows quality or regulatory reviewers to trace which version was in effect for a given batch, order, or time period.

  • characteristic number

    A characteristic number is a unique identifier assigned to a specific requirement, feature, or attribute on an engineering drawing or specification. In regulated manufacturing environments, it is commonly used to link each requirement to inspection records, data entry fields, or quality documentation for traceability.

    How characteristic numbers are used

    In practice, characteristic numbers typically:

    • Appear on ballooned or numbered engineering drawings next to dimensions, notes, tolerances, and other requirements
    • Map directly to line items in inspection forms, electronic inspection plans, or FAI (First Article Inspection) reports
    • Provide a stable reference for recording measured values, results (pass/fail), and any associated nonconformances
    • Support traceability between design requirements, shop floor inspection activities, and quality records in MES, QMS, or FAI software

    Each characteristic number should be unique within the scope of the drawing or inspection plan so that a reviewer can unambiguously connect the documented result back to the original requirement.

    What a characteristic number is not

    • It is not the measured value itself; it is a reference that points to the requirement being measured.
    • It is not inherently a risk or criticality rating, although systems may separately flag some characteristic numbers as key, critical, or safety-related.
    • It is not limited to dimensional data; it can also identify notes, material requirements, finishes, processes, or documentation checks.

    Common context in aerospace and AS9102

    In aerospace first article inspection (AS9102), each requirement on the ballooned drawing is assigned a characteristic number. That number is then used in the AS9102 Form 3 (characteristic accountability and verification details) to:

    • Identify the requirement being verified (dimension, note, specification, etc.)
    • Record measured results and inspection methods
    • Document any nonconformances related to that requirement

    This linkage helps auditors and customers confirm that every identified requirement on the drawing has a corresponding inspection record, without implying approval or compliance on its own.

    Common confusion

    • Characteristic number vs. balloon number: On many drawings these are effectively the same, because each balloon on the drawing contains the characteristic number. Some organizations use the terms interchangeably.
    • Characteristic number vs. characteristic ID in software: Digital systems may generate internal IDs that differ from the visible drawing number. In that case, the system should still preserve the original characteristic number as a reference back to the drawing.
    • Characteristic number vs. critical characteristic: A critical or key characteristic is a classification of importance or risk. The characteristic number is simply the identifier; separate attributes or flags usually indicate criticality.

  • back-to-birth traceability

    Back-to-birth traceability commonly refers to the ability to trace a part, material, or assembly back through its complete origin and transformation history, from its current state to the earliest recorded source or creation point. In manufacturing, this usually includes links across lot or serial records, supplier sources, processing steps, inspections, rework history, and as-built or maintenance records where applicable.

    It is a traceability concept, not a single document or software feature. The term describes the connected record chain needed to answer questions such as where an item came from, which materials or subcomponents went into it, which operations were performed, and which records support that history.

    What it typically includes

    • Material or component source information, such as supplier, batch, heat, lot, or serial number

    • Links between parent assemblies and child components

    • Production or processing history, including routing steps, work orders, and operation completion records

    • Inspection, test, and nonconformance records tied to the specific item or batch

    • Changes introduced through rework, replacement, repair, or disposition activity

    • Supporting genealogy across MES, ERP, QMS, PLM, or maintenance systems when records are distributed

    Depending on the industry and product lifecycle, the starting point for the item’s “birth” may mean raw material creation, original part manufacture, first assembly, or first controlled record in the enterprise system. Because usage varies, organizations often define the boundary explicitly.

    What it does not mean

    Back-to-birth traceability does not automatically mean full lifecycle traceability from design through retirement, and it does not guarantee forward traceability to every downstream customer or asset unless those links are also maintained. It also does not mean that every record is held in one system. The key idea is record linkage, not storage location.

    Common confusion

    Back-to-birth traceability is often confused with genealogy, lot traceability, and chain of custody. Genealogy usually focuses on the parent-child relationship of materials, subassemblies, and finished goods. Lot traceability may stop at batch-level links rather than serial-level history. Chain of custody emphasizes who possessed or transferred an item, which is narrower than the full manufacturing and quality history.

    It may also be confused with as-built records. An as-built record describes the configuration actually produced, while back-to-birth traceability refers more broadly to the evidence trail that connects that configuration to its origins and intervening events.

    How it appears in operations

    In practice, back-to-birth traceability appears as linked identifiers and records across receiving, production, quality, and maintenance workflows. For example, a serialized aerospace component may be traceable back to its raw material heat, supplier certificate references, machining operations, inspection results, rework events, and the work order under which it was completed.

  • material heat number

    A material heat number is a unique identifier assigned by a metal mill or foundry to a specific batch of metal produced in a single melting operation, often called a heat. It links finished parts and stock material back to the original melt, chemical composition, and test records documented on the mill test report or material certificate.

    In industrial and regulated manufacturing, heat numbers are used to maintain traceability from raw material through manufacturing, inspection, and final assemblies. The number is typically marked on bars, plates, forgings, castings, or on attached tags and packaging, and is recorded in receiving, inventory, and production records.

    What a material heat number includes

    A material heat number commonly:

    • Identifies one metallurgical batch from a single furnace melt or heat
    • Links to a specific material grade, specification, and chemistry
    • Connects to mechanical test results (for example tensile or hardness data)
    • Appears on the mill test report / material test report (MTR/MTRR)
    • Is carried into ERP, MES, and quality records for genealogy and traceability

    Manufacturers may subdivide a heat into internal lots or batches for handling and production control, but those lots normally all reference the same original heat number.

    Operational use in manufacturing and traceability

    In practice, material heat numbers are used to:

    • Verify that received material matches purchase order and specification requirements
    • Record which heat of material is used on each work order or serialized part
    • Support product genealogy and backward traceability for safety-critical components
    • Enable targeted containment, recall, or investigation if a material nonconformance is found
    • Demonstrate material traceability during customer or regulatory audits

    Typical systems that store heat numbers include ERP, MES, inventory management, laboratory information systems, and quality systems. On the shop floor, heat numbers may be captured on travelers, labels, barcodes, or in digital work instructions.

    Common confusion

    • Heat number vs. lot number: A heat number identifies a melt of metal at the mill. A lot number is a broader term that can refer to any grouped quantity of material or parts at a given organization. One heat may be split into multiple lots, but the original heat number usually remains as a reference.
    • Heat number vs. serial number: A heat number applies to a batch of material. A serial number is typically unique to a single finished item or component.
    • Heat number vs. batch number in other industries: In non-metal industries, batch numbers serve a similar traceability role but are not usually called heat numbers unless molten processing is involved.

    Relation to safety-critical and regulated components

    For safety-critical, aerospace, medical device, and other regulated components, traceability often extends from the finished assembly back to the raw material heat number. Maintaining a clear link between the component, the work order, and the source material heat supports investigations, risk assessments, and evidence requirements in quality management and compliance audits.