Skip to content
NPB NDT Consulting

Data and digitalisation

Inspection data needs identity and context

A result status alone may be difficult to explain later. Traceability starts with unambiguous association.

2 min readUpdated: Editorial team: NPB NDT Consulting

Maintain component identity throughout

Define whether results belong to an individual component or an agreed batch. The identifier must remain traceable through preparation, inspection, evaluation and documentation. Repeat inspections, manual diversion or line interruptions are particular opportunities for gaps in association.

NPB NDT Consulting

Inspection data with traceable context

A result value becomes reliable evidence through its assignment.

  • Component identity

    Component or batch ID

    Unambiguous assignment

  • Inspection context

    Instruction and program version

    System and reference

  • Inspection data

    Time and agreed data

    Scope defined per project

  • Evaluation and roles

    Result status and criteria

    Responsibility and clarification steps

Digital inspection record

Link data and documents

Traceable records for quality and production.

Conceptual illustration. Data scope, interfaces and retention are defined for each project.

Keep the context with the result

The record may include inspection time, system, method, program version and a link to the inspection instruction. Define the required raw data for the task. A later reader must be able to distinguish the original result, a repeat inspection and a subsequent reassessment.

Plan interfaces and data ownership together

A file export alone does not create an unambiguous exchange. Systems also need consistent interpretations of meaning, units and status values. Agree access rights, retention, backup and change handling. This provides the basis for deciding which connections to quality or production systems are actually needed.

Practical checklist

  • Define component or batch association
  • Link program and document versions
  • Identify repeat inspections explicitly
  • Agree status meanings, access and retention

Planning example

Illustrative planning example, not a customer reference.

Planning example: A component is inspected again. The second record links to the first without overwriting it. The responsible role documents which evaluation governs the next process step.

Key takeaway

Traceability depends on reliable relationships between data. A large volume of data is not, by itself, a traceable record.

Technical sources

The articles and method descriptions provide general technical orientation. The organisations listed are technical sources, not customers or partners of NPB NDT Consulting. Sources may be in German or English.

These articles provide technical orientation. The specific inspection task and applicable requirements must be assessed for each project.

Would you like to apply this question to your component or process? Start by describing the task in general terms.

Discuss your inspection task

Related articles