ACOUSTIC DETECTION · BUYER & TECHNICAL GUIDES / 622
Acoustic sensor procurement: Naming What Is Being Bought in the Bill of Materials
Acoustic sensor procurement becomes difficult when one label is used for a microphone, an array board, a processing module, and a complete detector. A useful bill of materials names the assembly level, function, ownership, revision, and included documentation so a supplier can quote the same object the engineering team intends to buy.
KEY TAKEAWAY
Acoustic sensor procurement starts with the assembly level
Treat the microphone, array acquisition electronics, acoustic processing, application software, enclosure, and finished detector as separate possible deliverables. Give each one its own line or structured subassembly, identify whether it is purchased or customer-built, and connect every line to an ordering code or controlled drawing. This prevents a board quotation from being mistaken for a working detector quotation.
01
Acoustic sensor procurement starts by naming the assembly level
The first purchasing error is usually a scope error rather than a component error. Words such as sensor, array, module, and detector can describe different points in the product hierarchy.
A microphone is a transducer or packaged component that converts sound pressure into an electrical signal. An array board may add several microphone positions, analogue conditioning, digitisation, connectors, timing, or local control. A processing module may receive channels and produce derived acoustic information. A complete detector may add an enclosure, power arrangements, firmware, classification logic, user interface, communications, documentation, and acceptance activities. These are not interchangeable names.
Use a parent-child structure when the product is built from assemblies. For example, a finished detector can contain an acoustic head, an acquisition board, a processing module, and software. The child lines describe what is inside the parent; the parent line describes what the customer receives as an assembly. This lets procurement request either a replacement board or a complete unit without making the supplier infer the boundary.
Write function and physical boundary together
A line named ‘acoustic sensor’ is too broad on its own. Add a short function statement such as ‘single microphone component,’ ‘multichannel acquisition board,’ or ‘edge acoustic processing module.’ Then state whether the item includes a connector set, firmware, enclosure, cable, or test record. The description should answer what is being bought and what is deliberately outside the line.
Use level codes that survive translation
A neutral level field is often more reliable than marketing language: component, subassembly, module, finished equipment, or software deliverable. Keep the same level concept in English and Traditional Chinese. Translation should not turn a board into a complete system or turn an algorithm licence into a physical part.
02
A microphone component is not a complete drone detector
A microphone can be essential to an acoustic product while still being only one input component. Procurement should avoid treating the presence of a sensing element as proof that detection, classification, or user presentation is included.
The microphone line should identify the actual part or approved internal specification, package, interface, quantity, and any required matching or inspection information. It should not silently include a board, signal conditioning, sampling, compute, model, communications, or enclosure. If the customer will mount the microphones on its own board, the bill should show that board as a separate customer-built assembly or a separate purchased line.
A complete detector is a product-level scope. It may accept acoustic channels, process them, and present an event or classification, but the meaning of that output still needs a documented definition. Detection, direction, localization, and classification are different outputs. A bill should therefore identify the expected output interface rather than implying that every acoustic component delivers every higher-level function.
Separate acoustic input from interpretation
The input stage records or digitises acoustic information; later stages interpret it. A procurement line can say ‘microphone element, purchased component’ while another says ‘classification software, project-scoped deliverable.’ This separation makes it easier to test, replace, or approve each layer without overstating what the microphone itself can do.
Avoid capability leakage from a product family
A supplier catalogue may discuss a full acoustic detection family while quoting only a module. Copying the family description into the BOM can make optional or higher-level functions appear included. Ask the supplier to mark included, optional, customer-supplied, and excluded items for the exact quoted configuration.
03
Keep array electronics and classification software in distinct scope descriptions
An array board and a software model may work together, but they remain different procurement objects with different revisions, tests, and support questions.
Array electronics can include microphone interfaces, analogue-to-digital conversion, clocking, buffering, field-programmable logic, network interfaces, or service connectors. Record the board identifier, hardware revision, channel definition, required host interface, and included firmware. Do not replace this information with a broad phrase such as ‘array sensor.’ The board may deliver channels or preprocessed data without delivering a final classification.
Classification software should have its own line or software subassembly. Name the supported processing host, release or model identifier, input format, output vocabulary, licence or entitlement basis, and documentation included in the project scope. A software line can be delivered by the supplier, supplied by the customer, or jointly reviewed. Those ownership choices should be explicit rather than hidden inside the board description.
Ask for the boundary between firmware and application software
Firmware that starts a board, moves samples, or manages a hardware interface is not the same deliverable as an application that classifies acoustic events. The BOM can identify both under one parent module while retaining separate child lines. This helps change control, acceptance testing, and replacement decisions when only one layer changes.
Describe outputs without promising performance
Use output terms such as channel data, event record, direction estimate, or classification label only when they are part of the agreed interface. Do not turn a nominal class label into confirmed identity, intent, or guaranteed accuracy. Site noise and integration conditions remain separate validation topics, not reasons to blur the BOM boundary.
04
Assembly-level ordering codes should not be replaced by ambiguous names
A readable name helps a buyer, but the controlled identifier protects the order. Both belong in the BOM.
Use the supplier’s assembly part number, customer drawing number, or approved configuration identifier alongside a plain-language description. Add revision, quantity per parent, unit of measure, and status such as approved, quotation-only, or pending review. If a supplier has not assigned an ordering code, use a temporary internal identifier and mark it as provisional rather than presenting a descriptive phrase as if it were a purchasable part.
Reference-design documentation illustrates why this matters: a design can list component reference designators, manufacturers, part numbers, assembly drawings, schematics, and a BOM as separate design records. Your purchasing BOM need not reproduce every design file, but it should point to the controlled record that defines the requested assembly. A photograph or family name is not a substitute for a revision-specific identifier.
Capture what changes the quote
State whether the code includes populated PCBAs, loose components, programmed memory, enclosure parts, cables, test fixtures, or documentation. Also identify any approved alternates and who may approve a substitution. A substitute at the microphone level can affect acoustic interpretation; a substitute board can affect interfaces and software dependencies.
Keep commercial and technical revisions aligned
The purchasing revision, engineering revision, and software release may not share one number. List them separately when they govern different deliverables. A quote should say which combination is being priced, so a later purchase order does not accidentally mix a current board with an older firmware or an unapproved model.
05
Show purchased and customer-built assemblies as different ownership lines
The same physical product can be assembled from supplier parts and customer work. A useful BOM makes that responsibility visible before quotation.
Mark each line as supplier-furnished, customer-furnished, customer-built, third-party licensed, or not included. For a customer-built acoustic head, the supplier may provide a board and interface documents while the customer supplies the housing, harness, power conversion, and final assembly. For a purchased detector, those items may be included in the finished-equipment line. The two configurations should not share one vague item name.
Ownership also affects incoming inspection and support. The buyer can inspect a supplier-furnished board against its drawing, while a customer-built enclosure may need a separate fit, cable, and acoustic-path review. If the customer supplies software or a host computer, state the prerequisite and the handoff point. This prevents a supplier from being asked to quote or warrant a complete product when only a core module was requested.
Use a responsibility matrix beside the BOM
For each assembly, identify who designs it, buys it, builds it, programs it, tests it, accepts it, and supports it. The matrix can remain short. Its purpose is to expose gaps such as a board that has an interface owner but no named party responsible for the host application or final enclosure.
Treat local assembly as a defined project path
Local assembly can be a delivery option rather than an automatic property of a module. Record which drawings, training, fixtures, quality records, and acceptance steps are included in the agreed scope. Do not assume that a local-assembly discussion means a complete local manufacturing service, certification, or universal support commitment.
06
A supplier can quote accurately only when each requested assembly level is clear
A quote request should turn the product hierarchy into a small, reviewable package. The goal is not to force one supplier’s terminology, but to make comparison possible.
Send the supplier the intended parent product, the required child assemblies, quantities, revisions, customer-supplied items, and desired deliverables. Ask for a line-by-line response that labels included, optional, excluded, and supplier-recommended items. Request separate treatment for hardware, programmed firmware, software, documentation, engineering services, and any validation work. This produces a comparable quotation without asking for an invented all-in price.
When the scope is uncertain, request alternate configurations rather than one blended line. For example, ask separately for an array acquisition board, a processing module, and a complete detector assembly. The buyer can then compare the integration work it retains against the work the supplier would perform. New Ark describes PCBA delivery, array acquisition, algorithm modules, and system interfaces as project-specific boundaries; the same discipline should appear in the buyer’s own BOM and purchase request.
Make exclusions useful
An exclusion should name the missing object: microphones, enclosure, host computer, application software, installation, or acceptance test. ‘System not included’ is less useful than a list of the assemblies the buyer must source or build. Exclusions are especially important when a product image shows a complete arrangement but the requested line is only a board.
Close the loop at purchase-order release
Before release, compare the supplier quotation with the BOM, drawing list, interface description, and responsibility matrix. Resolve mismatched quantities, revisions, software entitlements, and ownership labels. Keep the accepted configuration with the order record so receiving can verify what arrived without relying on a brochure name.
QUESTIONS FOR YOUR PROJECT
Acoustic sensor procurement buyer checklist
- Does every line state whether it is a component, subassembly, module, finished detector, or software deliverable?
- Is the physical boundary clear, including microphones, PCBAs, enclosure, cables, power, firmware, and documentation?
- Does each purchased assembly have an ordering code, drawing, revision, or clearly marked provisional identifier?
- Are array acquisition, processing, classification software, and user application described as separate scope items?
- Which items are supplier-furnished, customer-furnished, customer-built, licensed, optional, or excluded?
- Does the quote identify the input and output interface without turning a classification label into an identity or performance promise?
- Are approved alternates, change approval, inspection records, and support responsibilities recorded?
- Can receiving match the delivered assembly to the accepted BOM and configuration record?
REFERENCES
Sources for this article
Publisher names, dates and relevant contributions are listed below. Confirm offered product details with the supplier.
National Institute of Standards and Technology, Microphone Array Presentations · Updated August 27, 2025
Supports the distinction between microphone-array acquisition boards, motherboard aggregation, digitisation, FPGA processing, firmware, and software/data-flow functions.
Texas Instruments, TIDEP-0099 Audio Preprocessing System Reference Design · July 6, 2017
Supports describing a modular audio solution through microphones, a microphone board, DSP processing, software, assembly drawings, schematics, and a separate BOM record.
New Ark, PCBA Delivery · Accessed 2026-11-20
Supports project-scoped language for array acquisition cards, algorithm processing modules, system interfaces, local assembly discussion, and written technical boundaries.
ARTICLE FAQ / 622
Questions on Acoustic sensor procurement: Naming What Is Being Bought in the Bill of Materials
Practical questions about this article and the proposed product scope.
RECORDACOUSTIC DETECTION LIBRARY
TALK TO NEW ARK
Turn a component list into a reviewable delivery scope
If your team is comparing a complete acoustic detector with array or processing modules, share the intended assembly levels, interfaces, and customer-built items with New Ark. A project-scoped review can separate PCBA delivery, software boundaries, and system integration questions before a quotation is prepared.

