Permanent UT Monitoring: Sensor and Data Acceptance Guide
A permanent ultrasonic sensor can provide repeated information at an installed location. The useful purchase is the complete route from that defined point to an interpretable time series, including missing data, configuration changes and the people who review the result.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Define the monitoring question before counting sensors
Identify the asset-management question the proposed monitoring system is intended to inform. The integrity owner should define the relevant locations, required measurement evidence and decision process. Purchasing should not choose sensor quantities from a general promise of continuous visibility. A sensor count describes hardware; it does not establish that the selected locations represent every degradation concern on the asset.
Write a monitoring brief containing the asset, proposed point identities, intended output, technical owner, review responsibility and required data destination. This guide addresses package selection and data acceptance. It does not prescribe sensor placement, installation methods, alarm limits, inspection intervals or integrity decisions. Those belong to qualified personnel and the applicable site process. The buying task is to ensure that the selected equipment and service can produce the evidence that process requires.
Separate point monitoring from area coverage
Emerson's ultrasonic monitoring overview describes permanently installed sensors measuring wall thickness at their installation points. That spatial limitation matters. Repeated measurements over time at a defined point do not automatically establish the condition of the surrounding surface, an entire pipe circuit or every location where damage could occur. Ask the integrity owner how the proposed points fit within the broader inspection strategy.
Keep the accepted spatial scope visible in reports and dashboards. A point plotted on an asset image should not be interpreted as coverage of the whole illustrated area. If the supplier proposes another configuration with broader measurement scope, evaluate that configuration separately. The procurement record should describe what is directly observed and what conclusions require additional evidence. This makes the monitoring package useful without overstating what a growing collection of time-stamped values can establish about unmeasured locations.
Distinguish the sensor, transmitter and data service
List the physical measurement elements, mounting arrangement, transmitter, communications infrastructure, software and review access. The exact architecture varies by product. Emerson's ET410 page describes a battery-powered ultrasonic thickness transmitter communicating through WirelessHART. Use that as a concrete example of why a sensor-only quote may omit essential dependencies needed to deliver a usable record.
Ask the supplier to identify what the organization supplies and what the package includes. A gateway, network integration, software license or commissioning service should not remain an unstated assumption. Assign an owner to each interface. The final quotation should connect the measurement point to the intended receiving application, including any separately priced services. A successful display on a supplier's demonstration network does not establish that the same data path is available at the customer's site.
Confirm the exact measurement technology and environment
Permanent UT product families can use different sensor arrangements and application approaches. Ask the supplier to identify the proposed model and its documented material, surface and environmental scope. Do not transfer a temperature or coating statement from one transmitter family to another. The technical and site owners should review the actual installed configuration, including the mounting arrangement and supporting components.
Record the evidence supporting each relevant condition and the items that remain unresolved. If a demonstration is performed on a different surface or under different conditions, preserve that limitation. The purchasing file should not translate a general technology advantage into authorization for an unreviewed installation. A clear model-specific response allows the organization to compare offers fairly and prevents later substitutions from being accepted solely because they carry the same brand or use the same communications protocol.
Establish a permanent point identity
Assign a durable monitoring-point identifier distinct from the sensor serial number. The point represents the intended physical measurement location; the sensor is an asset that may later be replaced. Associate the point with the asset hierarchy, location description and controlled drawings or photographs required by the organization. The technical owner determines the location definition, while purchasing ensures that the software and export can preserve it.
Test the relationship with fictional data. Replace a simulated sensor identity while retaining the same point identity, then confirm that the record shows both the continuity of location and the hardware change. Also test the opposite case: moving a sensor to a different approved point should not silently continue the old point's history. These are data-management scenarios, not installation instructions. They reveal whether the proposed system can keep long-term trends understandable as hardware changes.
Agree the baseline evidence and its ownership
Ask the technical owner what evidence is needed to establish the initial measurement record at a new point. The baseline may include configuration, supporting examination information and an acceptance decision under the organization's procedure. Purchasing should identify who supplies and reviews each artifact. Do not assume that the first value appearing on a dashboard is automatically an approved baseline for every later comparison.
Preserve the baseline's date, point identity, sensor identity and relevant context in the controlled record. If a portable measurement or another method is used for comparison, retain its location and scope rather than treating it as an interchangeable number. The technical owner decides how differences are evaluated. The package should support this documented review so a future user can distinguish an accepted starting record from provisional commissioning data or a value awaiting investigation.
Define what each timestamp means
Ask whether the system records measurement time, transmission time, receipt time and processing time, and which appear in each export. These can differ when communication is delayed. A value arriving now may describe a measurement made earlier. The data owner should define which timestamp drives the intended analysis and how the record communicates that distinction to reviewers.
Include time zone and clock behavior in the acceptance trial. Use nonproduction data spanning a planned interruption or a simulated delayed delivery. Check how the receiving system orders records and whether a later arrival can be mistaken for a newer physical measurement. Avoid silently rewriting timestamps during import to make a file easier to load. Preserve the supported meaning of the original fields and document any approved transformation so the resulting time series remains interpretable.
Separate measurement availability from network availability
A communications link can be active while a measurement is unavailable or requires review. Conversely, a valid stored measurement may arrive after a communications delay. Ask the supplier how those states are represented. Do not accept a single green connection icon as proof that every monitoring point has a current usable measurement. The technical and data owners should define the status information required for the intended workflow.
During the trial, inspect the exported records and dashboard behavior for missing, delayed and invalid examples supplied through an approved test plan. A missing value should not silently become zero or be carried forward as though it were a new measurement. Record how reviewers distinguish the last valid observation from the latest communication event. That distinction is central to a trustworthy monitoring service and should be evaluated before the organization relies on a live dashboard.
Ask how gaps and backfilled records are handled
Determine whether the proposed system stores measurements during communication interruptions, under what documented conditions and how recovered records are delivered. Do not infer unlimited local storage from a general continuous-monitoring description. Request the current product-specific explanation and have the data owner assess it against the intended service. The purchase should identify the supported behavior and its boundaries.
Use a controlled demonstration to review a gap followed by recovered records. Confirm that the recipient can distinguish an actual absence of measurement from a delayed transfer. Check duplicate handling and the relationship between original and corrected records. If the software draws a line across a gap, ask how the display signals that the interval contains no observed data. The technical reviewer should be able to understand the evidence without mistaking a convenient visualization for continuous measurement availability.
Keep trend calculations separate from measured values
Ask which outputs are direct measurement records and which are calculated trends, rates or other derived indicators. The integrity owner determines how such outputs may be used. Purchasing should require enough context to identify the calculation and the input records on which it depends. A rate displayed with several decimal places is not automatically more authoritative than the underlying evidence supports.
Check how the software handles a sensor change, a revised baseline, a data gap or an excluded record in a derived trend. The buyer need not choose the calculation method, but the responsible reviewer should understand the supported behavior. Retain the configuration or version information required by the organization's process. If a supplier service provides the interpretation, clarify its scope and review responsibilities rather than assuming the hardware purchase includes an ongoing integrity assessment.
Define alerts as a workflow with an owner
If monitoring software offers alerts, identify the event type, recipient role, delivery route and required acknowledgment process. Technical thresholds and response actions belong to the authorized integrity process. The procurement trial should demonstrate the agreed notification path using fictional events and show how users distinguish a measurement concern from a communications or equipment-status issue.
Record what happens when the intended recipient changes roles or an integration becomes unavailable. An alert appearing in a supplier portal may not reach the person responsible for action. Assign an owner for account and routing maintenance. Do not describe monitoring alerts as automatic authorization to continue or stop operation; the organization's approved process governs those decisions. The purchased system should support that process with clear evidence and reliable routing within its documented scope.
Plan sensor replacement without erasing history
Ask how the data system records replacement, relocation and configuration changes. Preserve the earlier sensor identity and the effective point of change. The technical owner decides what evidence is needed before the new arrangement is accepted. Avoid merging records merely because both devices report to the same dashboard tile. A long-term trend should allow the reviewer to identify where its measurement arrangement changed.
Use a fictional replacement in the acceptance dataset. Confirm that the exported history retains both sensor identities and relevant status information. If the system creates a new series, document how the organization associates it with the established point. If it continues one series, document how the transition is marked. Either design may be workable when its meaning is clear. The unacceptable outcome is an undocumented discontinuity that later reviewers cannot distinguish from an actual change in the asset.
Work through a fictional stale-value display
A hypothetical facility installs a trial monitoring package at several approved points. During an agreed network interruption, the dashboard continues displaying the last received value. On reconnection, older stored measurements arrive. The buyer asks the supplier to demonstrate how the screen and export distinguish the last valid measurement time, current communication status and newly received historical records. A familiar-looking graph alone does not answer those questions.
The data owner adjusts the supported display and import workflow so reviewers can see the relevant status. The integrity owner confirms how that information fits the approved review process. The package is accepted with its documented limitations. This fictional example illustrates a records risk rather than a claim about a named product: a system can preserve useful measurements while still needing careful time and status handling to prevent users from misunderstanding what is current.
Price the complete retained-data obligation
Include the required software access, data export, storage, account administration and support in the commercial comparison. Ask who owns the records and what access remains if the service ends or the supplier changes the platform. Test an actual export before treating the phrase data ownership as sufficient. The organization should be able to receive the agreed identity, time, units and status fields in a usable form.
Define the responsibility for ongoing maintenance of point records and interfaces. A monitoring installation is not a one-time hardware handover if its value depends on a continuing data service. Preserve current commercial terms and supported retention arrangements. The buyer can then compare complete service obligations rather than contrasting a bare sensor price with a proposal that includes commissioning, software and support. Avoid assuming that a long battery-life claim eliminates every other maintenance or administrative dependency.
Close commissioning with a readable point history
Acceptance should produce a sample history that an authorized reviewer can interpret without the supplier narrating it. The record should identify the point, sensor, baseline, units, measurement time, status, relevant changes and any gaps. Keep the technical commissioning evidence and data-interface evidence associated but distinguish their owners. A functioning network connection should not be the only recorded basis for acceptance.
NDT Connect can track the physical equipment's identity, due date, status and notes. It does not ingest monitoring streams, calculate corrosion rates or issue integrity alarms. Keep those functions in the selected monitoring and asset-management systems. The equipment record can reference the controlled point and commissioning file. A complete purchase leaves the organization with a defined measurement service and an understandable history, including the limits of what was observed and when it became available.
Preserve rejected commissioning records without using them as a baseline
The initial dataset may contain provisional records created while the authorized commissioning process is still underway. Ask how those records are labeled and retained. A later reviewer should be able to distinguish them from the accepted monitoring history without relying on a separate verbal explanation.
Have the technical owner record the accepted starting boundary and the reason for excluding earlier records from the intended trend. Keep the original evidence available according to the organization's retention process. The data system should support an explicit disposition rather than requiring users to delete inconvenient values simply to produce a clean-looking graph.
Frequently Asked Questions
Does one permanently installed sensor establish area coverage?
No. Establish the spatial scope and point selection through the integrity program; repeated point measurements do not automatically describe surrounding unmeasured areas.
Which time should be retained?
Define the required measurement, transmission and receipt-time meanings with the data owner; delayed delivery should not be mistaken for a new physical measurement.
Should a replacement sensor simply overwrite the old identity?
No. Preserve the hardware transition and the technical review needed to interpret continuity of the point history.
References & Standards Cited
- Emerson: ultrasonic thickness monitoring system scope View source ↗
- Emerson: Rosemount Wireless ET410 thickness transmitter View source ↗
Related on NDT Connect
Join NDT Connect — free
The free marketplace for the NDT industry — connect inspectors and the companies that need them.
Free to join · Compare provider qualifications and confirm availability directly · Browse providers
By NDT Connect Editorial · Updated
Source-based editorial guidance. Read our editorial policy and disclosures.