NDT Instrument, Probe and Block Records: Map the Relationships

Distinguish an item from a kit and a measurement configuration

An individual item is the physical object whose identity and history you control. A kit is a convenient grouping for storage, transport or assignment. A measurement configuration is the arrangement relevant to a defined technical activity. These concepts overlap, but they are not interchangeable. A case containing several components does not prove that those components were used together on a particular examination.

The international metrology vocabulary recognizes that a measuring system may include one or more instruments and associated devices. The administrative consequence is to preserve the relevant component relationships when the technical process requires them. It does not mean that every loose accessory needs an independent calibration record or that a packing list establishes technical suitability. JCGM measuring system

Agree which question each record answers. The equipment register identifies items. The kit list describes current contents. The job or technical record identifies the configuration actually used where required. Keeping these purposes explicit avoids an overloaded spreadsheet that appears comprehensive but cannot answer a precise historical question.

Decide which components need independent identities

Ask the technical and equipment owners which components have separate evidence, service history or substitution controls. Serialized probes and individually identified reference blocks may require their own records. Other accessories may be adequately controlled by description and quantity. Document the boundary rather than assuming every organization must use the same level of detail.

An independent identity is particularly useful when a component moves between instruments. If a probe appears only as free text inside one instrument's record, moving it can erase its earlier association. A stable component reference allows the history to continue while the current kit or instrument relationship changes.

Do not manufacture a manufacturer serial where none exists. If your process requires an internal component identifier, label it as internal and establish it through the approved identification process. Preserve any original marking separately. Avoid changing or attaching physical markings in ways that conflict with manufacturer instructions or the organization's equipment controls.

Create an association record with a time boundary

A useful association identifies the component, related instrument or kit, start event and end event. It also identifies who recorded the change and the evidence reference if one is needed. The time boundary matters because a current kit list cannot explain which components were present months earlier after several exchanges.

Use a separate association row for a new relationship instead of overwriting the previous component entry without history. A small spreadsheet can manage this with one row per association period. It need not be a complex database, but it should let a colleague distinguish the present relationship from a past one.

Record uncertainty honestly. If the exact transfer date is unknown, state the known evidence and the unresolved period. Do not select an arbitrary date merely to make the history look complete. The technical owner can decide whether the missing timing matters to any record or assignment requiring review.

Give temporary associations an explicit end condition. A probe borrowed for one assignment should not remain indefinitely listed in the receiving kit because nobody recorded its return. Name the person who confirms the return and reconciles both kit lists. If the planned end date passes without confirmation, treat that as an open custody question rather than automatically closing the association. This makes temporary transfers visible without creating a false history of where the component was physically held.

Keep approval separate from physical association

A component can physically fit in a case or connect to an instrument without being approved for the intended technical use. The association log should therefore avoid labels such as compatible or qualified unless they reference an actual authorized decision. Use neutral language such as packed with, assigned to or received with for ordinary custody relationships.

When a technical configuration is controlled, record its approved reference in the appropriate technical system. The equipment coordinator can connect that reference to item identities, but should not recreate the technical requirements from memory in the inventory notes. Duplicating technical instructions in several administrative locations creates opportunities for inconsistent revisions.

If staff propose a substitution, route it to the authorized technical person. Record the proposed component and the decision reference. A matching model name or a recent certificate does not automatically approve substitution. The guide provides a record structure, not a list of permissible instrument-and-probe combinations.

Connect evidence to the item or configuration it describes

Read the identification scope of each certificate or service document. Some evidence describes an individual component; other evidence may identify a complete arrangement or several listed items. Associate the record with what the issuer actually identified. Do not attach one instrument's certificate to every accessory merely because they shared a shipment.

Where a document lists several components, retain the list and its relationship to the document issue. A later component exchange should not silently make the old document appear to cover the new arrangement. Ask the technical reviewer what evidence remains applicable and what additional review is needed.

Use stable evidence references rather than copying full documents into every item's folder without version control. Multiple copies can diverge when a certificate is amended. A shared reference with clear access and revision handling often makes it easier to establish which document was reviewed for each relevant item.

Manage transfers between kits as real events

At a transfer, identify the item leaving one kit and the item entering the other. Update both affected kit lists. A common error is adding a component to the receiving kit while leaving it listed in the sending kit, creating a fictional spare. Record the transfer reference so the two updates can be reconciled.

Check whether the transfer changes any planned assignment. The dispatch coordinator needs the actual available population, and the technical owner may need to review a configuration change. The equipment record should communicate the event without implying that the administrative transfer itself completes that technical review.

Do not use a case's location as a reliable proxy for every component's location after exchanges begin. If the organization needs item-level custody, maintain it at the appropriate level. The required detail should follow real retrieval and control needs, not the convenience of assuming the contents never change.

A hypothetical shared-probe history

A fictional shop controls instruments EQ-061 and EQ-062, probe PR-014 and block RB-008. Initially, PR-014 is packed with EQ-061 in kit A. The technical records for an assignment identify the actual approved configuration separately. The current kit list is useful for dispatch but is not presented as the examination record.

Later, PR-014 moves to kit B after the authorized owner reviews the proposed use. The coordinator closes the kit A association and opens the kit B association, referencing the transfer. The probe's identity and service history stay unchanged. RB-008 remains independently controlled and is not assumed to have moved just because the probe did.

A reviewer investigating an earlier assignment can now see both association periods and retrieve the relevant job record. Without the time-bounded association, the current kit B list could incorrectly suggest that the probe had always belonged to EQ-062. This example is fictional and provides no technical approval for any equipment combination.

Handle replacement components without recycling history

When a component is replaced, establish whether the returned object is the same item repaired or a different item supplied in exchange. A new serial or an explicit replacement record may indicate a new physical identity. Preserve the service connection, but do not write the replacement serial over the old item's identity as though nothing changed.

Close or revise the old association and create the new one with the actual replacement event. Retain the withdrawn component's evidence under the applicable retention process. Historical technical and job records should still be interpretable using the identifiers that existed when the work occurred.

Ask the technical owner to identify any configuration or document review caused by the replacement. A supplier's commercial description of an equivalent part is not your organization's technical authorization. The coordinator should make the change visible and assemble the evidence needed for the appropriate decision.

Use a relationship worksheet alongside the current tracker

The downloadable association log is a separate spreadsheet aid. It includes kit and component references, association dates and an optional approved-configuration reference. These columns are not dedicated NDT Connect features, and the worksheet is not an import file or a configuration approval form.

The free tracker records individual equipment name, type, serial, manufacturer, model, calibration due date, status and notes. It has no dedicated component hierarchy, kit relationship table or immutable transfer history. You can use concise notes to reference a controlled relationship record, while retaining the detailed associations in your own system.

Avoid duplicating the same physical component as several equipment records solely because it is used with several instruments. That approach creates competing dates, statuses and reminders. Maintain one stable item identity and express its different associations separately, with the appropriate time and purpose attached to each relationship.

Review relationships using a practical retrieval exercise

Select a current kit and compare its listed contents with the physical population. Then select a past assignment and ask whether the records identify the relevant historical configuration. These exercises test different capabilities. A successful current count does not prove that historical associations were preserved, and a complete job file does not prove today's kit list is accurate.

Investigate discrepancies using transfer, shipment and service evidence. Record the actual scope checked and unresolved questions. Do not quietly normalize the list to whatever is present without considering whether a component is missing, duplicated elsewhere or awaiting an authorized substitution decision.

Improve the handoff where errors occur. If transfers are missed, simplify the transfer record and name the updater. If documents are attached at the wrong level, clarify item-versus-configuration evidence rules with the technical owner. The objective is a reliable connection among physical items, changing groups and the records that actually describe them.

Complete the association worksheet with an actual event sequence

Start the worksheet with one physical component and follow its movements. Enter the component identity, related kit or instrument, association start event and the source record. When the relationship ends, add the end event without changing the original start. The purpose is to represent a period or event accurately, not to make every row appear current.

For a fictional probe PR-014, the first row records its assignment to kit A on November 2. A transfer record establishes movement to kit B on November 8, so the first association closes and a new one begins. If the exact time matters to a particular assignment, retain the available timing evidence and route any ambiguity to the technical owner. Do not invent a midnight boundary solely because the worksheet accepts dates more easily than times.

A shared reference block may have a different relationship pattern. It can be stored centrally and issued temporarily to several kits at different times. Record the actual custody or assignment events your process requires rather than creating a permanent association with every instrument that could potentially use it. Potential suitability and actual possession are different relationships.

Review the completed rows for impossible overlaps, missing end events and components listed simultaneously in unrelated locations. An overlap can be legitimate if the records describe different relationship types, such as approved candidate and actual custody, but those types must be explicit. If the rows are intended to describe physical custody, investigate the conflict instead of explaining it away through vague kit terminology.

Use a historical retrieval drill to test the relationships

Choose an earlier assignment for which the organization needs a defined equipment record. Ask an authorized colleague to identify the relevant instrument and controlled components from the proper job and association records. Then ask them to retrieve the supporting evidence issues. The exercise tests whether relationships help navigation; it does not ask the colleague to infer technical approval from an inventory list.

Include a case where a component moved after the assignment and a case where a replacement was introduced during service. These events expose whether the current relationship has overwritten the past. A system that can only display today's kit contents may still be useful for dispatch, but it needs a separate route to the historical configuration where that is required.

Record the precise failure if retrieval is difficult. The problem might be an missing transfer reference, a reused internal identifier, an inaccessible certificate or a job record that does not identify the required population. Each needs a different correction. Adding a new relationship column will not repair missing original evidence automatically.

For a fictional review, the colleague finds PR-014 in kit B today but follows the dated association to kit A during the selected assignment. The job record then supplies the actual configuration reference. That is a successful use of the relationship index: it supports retrieval while preserving the distinction between a storage grouping and the technical record of work.

Retain the drill's scope and improvements in your administrative review record. Do not claim that one successful retrieval validates every historic configuration. Use the observed gaps to improve transfers and evidence associations where they occur.