Acoustic Emission Buying Guide: Channels, Waveforms and Records
A multichannel acoustic emission system is more than a chassis with spare slots. The buyer needs a defined sensor-to-record chain, the required waveform and feature storage, and enough context for an authorized analyst to understand the saved examination.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Define the examination record the organization needs
Ask the technical owner to describe the intended acoustic emission application and required deliverable. Identify the asset type, relevant test or monitoring context, expected analysis and record-retention obligations. Purchasing should not assume that a general AE product demonstration establishes suitability for every component or loading condition. The requested package must support a specific approved application and the evidence required to review it.
Keep technical test design separate from the equipment request. This guide does not select sensor spacing, acquisition thresholds, loading schedules, source-location models or acceptance criteria. Those require the responsible specialists and applicable procedures. The buyer's role is to obtain a complete configuration, clarify optional functions and demonstrate that the agreed data package survives acquisition, review and retention. That scope is substantial without attempting to turn a procurement checklist into an AE operating procedure.
Count complete channels rather than empty capacity
Vallen's multichannel-system description identifies a measurement channel as a chain including a sensor, preamplifier and signal-processing channel. A chassis capacity figure therefore does not necessarily equal the number of complete channels included in the quotation. Ask the supplier to list installed acquisition channels and the corresponding sensors, preamplifiers, cables and supporting hardware needed for the planned application.
Create a channel bill of materials with explicit quantities and identities where available. Distinguish populated capability from expansion capacity and future options. If the demonstration uses more channels than the offer includes, record the difference. A package may be a sensible starting point with room to grow, but the business case should not count unpurchased components as available measurement capability. The accepted configuration should make the actual complete-channel count understandable to a coordinator who was not involved in the sales discussion.
Distinguish extracted features from retained waveforms
The Vallen product page explains that its system extracts AE features and offers waveform recording through an optional transient-recorder function. Those are different data products. A list of event parameters is not the same as the complete recorded waveform. Ask the technical owner which records are required for the intended analysis and future review, then confirm that the necessary hardware, software and storage options are included.
Have the supplier provide sample files for the quoted configuration. The reviewer should identify which information is retained and which cannot be reconstructed from the proposed record. Do not assume that a visually detailed plot means every underlying waveform has been saved. If the organization deliberately chooses feature-only retention for a defined task, document that decision and its limitations. The important purchasing outcome is an explicit evidence choice, not the largest possible dataset without a clear review purpose.
Preserve the channel-to-location association
A channel number is only useful when its relationship to the physical sensor and examination location is known. Ask how the system stores that association and how it appears in exported records. The technical owner defines the sensor layout and necessary location information. Purchasing should require a supported way to retain the approved layout, sensor identities and relevant configuration with the examination data.
Use a fictional layout during the trial and ask another reviewer to trace a selected channel back to its documented sensor location. Include a controlled example of a channel reassignment so the team can see how changes are represented. Do not allow a later configuration to overwrite the meaning of earlier records. The archive should preserve the arrangement that applied to each examination segment, rather than relying on the current channel list to explain all historical data.
Include contextual inputs as their own measurement paths
An AE examination may require association with other recorded quantities or test context. Vallen's 2021 system description describes parametric input capability as part of its architecture. Ask which contextual inputs the intended application requires and what hardware, interfaces and evidence are included for them. Do not assume that an auxiliary input is ready for a particular external signal merely because the chassis has a connector.
Have the responsible owners define the source, units, scaling, time relationship and required verification for each contextual quantity. Purchasing should list these paths separately from AE channels and identify who supplies the external devices. During the data trial, confirm that the analyst can interpret the contextual record and its relationship to the AE data. A trend line with an unlabeled axis is not a complete demonstration of usable test context.
Match sensors and preamplifiers to the approved scope
Request the exact sensor and preamplifier models proposed for the application. The technical owner should evaluate their suitability and the supporting evidence. Avoid substituting components based solely on connector compatibility or a broad frequency label. A complete quote should identify the intended combinations and the documentation needed to review changes later.
Keep the association flexible enough to manage service while preserving the configuration actually used. The organization may not permanently dedicate one sensor to one channel, but it still needs a record of the relevant arrangement for an examination. Ask the supplier how identities are entered or recorded and what remains visible after export. If this requires an external equipment manifest, include it in the workflow and trial. A manual record can be useful when it is controlled and reliably associated with the dataset.
Define verification evidence for the whole chain
Vallen's system-verification resources distinguish equipment elements such as signal processors, parametric channels and sensors. Use that scope distinction to ask what evidence accompanies the offered package. A certificate for one component should not be represented as proof that every part of the assembled measurement chain has been evaluated for the intended application.
The technical owner determines the required verification approach and frequency under the applicable requirements. Purchasing obtains the agreed records and confirms their identities and scope. This guide does not reproduce verification procedures or specify universal limits. Retain baseline evidence from acceptance so later service or configuration changes can be reviewed against a documented starting point. If the supplier offers a verification software option, clarify what it does and what additional equipment or qualified review the complete process still requires.
Evaluate storage under the intended recording mode
Ask the supplier to demonstrate data handling with the recording functions the organization intends to use. A feature-only demonstration may not represent a workflow that also retains waveforms. Identify the computer, storage device and software version used. The technical team should define a representative trial dataset and recording context without relying on the most favorable promotional workload.
Review how the system reports capacity limits, interruptions or unavailable data. The buyer does not need to provoke unsafe test conditions to evaluate record behavior; the supplier can provide an approved controlled exercise or documented test evidence. Record the limits relevant to the intended service. A large nominal storage figure does not by itself establish that the whole acquisition and transfer path supports the required recording workload without an understandable account of what was retained.
Keep acquisition and analysis licenses distinct
Ask which software rights support acquisition, offline analysis, report generation and long-term reading. Determine whether an analyst can work with saved data while the field system is used elsewhere. A license attached to a particular computer or hardware unit may create a different workflow from a separate analysis license. Preserve the current terms for the exact offered package.
Demonstrate opening a retained project on the intended analysis workstation. Include the functions the reviewer actually needs, not merely file recognition. If a trial license supplies an advanced analysis feature, identify whether it is included in the purchase. The organization should understand which parts of the review depend on continuing subscriptions, support arrangements or additional modules. This makes the price comparison reflect the complete service rather than the minimum configuration needed to display an acquisition screen.
Preserve source-location assumptions as review context
If the intended application uses source-location analysis, ask what configuration and model information must accompany the dataset. The technical owner determines the appropriate approach and its limitations. Purchasing should verify that the software can retain the required context and that another authorized reviewer can identify what produced the reported location. Do not assume that a plotted point on a drawing is self-explanatory evidence.
Use an approved sample project to trace a reported location back to the relevant data and analysis configuration. Record which information is saved in the project and which is maintained externally. If the component drawing or sensor layout changes, preserve the version used for the examination. The buying requirement is a reviewable relationship between data and reported result, not a universal claim about location accuracy or a substitute for application-specific validation.
Work through a fictional waveform-option omission
A hypothetical laboratory requests a multichannel AE system for an application whose review process requires stored waveforms. The initial offer provides the desired channel count but includes only the feature-recording configuration. A supplier demonstration displays waveforms using an optional function. During the acceptance-plan review, the buyer asks for sample files from the exact quoted configuration and identifies the mismatch before ordering.
The technical owner confirms the required record, and purchasing obtains a revised offer with the necessary recording and analysis capabilities. The team repeats the sample-file trial and documents the workstation requirements. This fictional example does not allege a defect in a named system. It shows why channel quantity and retained-data capability must be separate quotation lines. A system can have the expected number of inputs while lacking an optional function essential to the organization's intended evidence package.
Define interrupted and excluded records clearly
Ask how the system marks an interrupted acquisition, a disabled channel and data excluded from a particular analysis. The technical owner controls the permitted treatment of those conditions. The software should allow the final record to preserve the distinction between observed data, missing evidence and an analytical exclusion. A report should not silently make those states look identical.
Review a nonproduction example with the intended analyst. Confirm that the retained project explains the examination segments and relevant configuration changes. If a report presents only a summary, determine where the supporting context remains accessible. The procurement decision should include any manual documentation needed to make that context understandable. This helps future reviewers assess the record without treating a clean graph as proof that every channel was continuously available throughout the examination.
Build a receiving manifest for channels and accessories
At receipt, reconcile the installed acquisition capability, sensors, preamplifiers, cables, synchronization items, parametric interfaces and software against the accepted configuration. Record serial identities where applicable and investigate unexplained substitutions. Count complete intended measurement paths, not only the number of boxes in the shipment. Confirm that the promised evidence corresponds to the delivered items.
Keep the manifest with the trial datasets and acceptance decisions. If some sensors are customer-supplied, identify their separate evidence and disposition rather than treating them as implicitly accepted through the new chassis purchase. The completed package should allow a coordinator to distinguish available components from a supported examination configuration. That distinction remains useful when equipment is shared between teams or sent for service after the initial project owner has moved on.
Close the data handover with an independent review
Ask an authorized analyst who did not prepare the trial to open the accepted sample package. They should identify the examination, channel layout, retained data types, contextual inputs, relevant configuration and known limitations. Record any missing information and close it through the agreed process. This is a practical test of whether the purchase delivers an understandable technical record rather than a system that only the demonstrator can explain.
NDT Connect can track the physical assets and their administrative status, dates and notes. It does not acquire AE data, synchronize channels, locate sources or archive waveforms. Keep those functions in the selected acquisition and analysis environment. Use the equipment record to reference the controlled configuration and acceptance file. The final purchase should leave a complete channel architecture, an explicit retained-data choice and a review path that remains usable after the original acquisition session.
Record expansion assumptions before buying spare capacity
If future expansion is part of the business case, ask which components, software rights and synchronization items will be needed. Separate documented available options from possible future development. Do not count empty slots as a complete expansion plan. The technical owner should review whether a larger configuration changes the evidence requirements for the intended application.
Retain the supplier's current compatibility statement with the purchase file. When expansion actually occurs, compare the delivered additions with that statement and obtain the required acceptance evidence. This makes spare capacity a useful planning feature while preventing it from becoming an unsupported promise that any later channel arrangement will inherit the original system's accepted scope.
Frequently Asked Questions
Does chassis capacity equal delivered AE channel count?
No. Confirm installed processing channels and the complete sensor, preamplifier and cable paths included in the offer.
Are feature records equivalent to stored waveforms?
No. They are different data products. Specify the required recording and review functions explicitly.
Why list auxiliary inputs separately?
Their source, units, timing and supporting evidence may be essential to interpreting the AE record and require their own hardware and review.
References & Standards Cited
- Vallen: AMSY-6 multichannel system architecture View source ↗
- Vallen: AMSY-6 System Description, November 2021 View source ↗
- Vallen: system verification scope and documentation 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.