An industrial sensor PCBA is ready for production when the released design, sensor handling instructions, firmware, calibration approach and acceptance tests describe the same product configuration. A board that powers on is only one part of that decision. The manufacturing handoff must also explain what the finished instrument measures, under which conditions, and what evidence releases a unit for shipment.
Use this industrial sensor PCBA production checklist when moving a temperature, pressure, humidity or similar measurement product from an engineering build to repeatable assembly. It focuses on the information exchanged between your engineering team and the manufacturer. It does not prescribe a universal sensor accuracy, calibration method or production test limit.
Start with the measurement requirement
Describe the intended measurement before listing assembly operations. Is the product measuring ambient air, a surface, a liquid or a remote transducer? Define its operating range, required system performance, response expectations and installation configuration. Include the reference conditions under which the product will be evaluated. Those decisions determine which production checks are useful.
A component specification is not automatically a finished-instrument specification. For humidity and temperature products, Sensirion’s design-in guide explains that enclosure design, airflow and internal heat sources can affect system behavior. Treat the PCB, enclosure and sensor location as one measurement arrangement when defining the build and test requirements.
Record the requirement owner and the approval date. If a performance target remains open, identify it in the project brief before requesting a fixed test sequence. The electronics RFQ checklist helps organize these open decisions alongside the board files and BOM.
Build a handoff matrix with named owners
Use the following table as a project worksheet. Replace each open item with a released document, a responsible person and a clear acceptance decision. An engineering drawing and a supplier email that disagree should be resolved before either becomes an operator instruction.
| Handoff item | Information to release | Evidence to retain |
|---|---|---|
| Sensor and BOM | Exact manufacturer part number, approved alternatives and configuration restrictions | Approved BOM revision and substitution decisions |
| PCB and assembly | Fabrication data, placement file, assembly drawing and polarity references | Matched file revisions and first-article review |
| Handling and protection | Relevant sensor instructions and explicit coating, cleaning or potting exclusions | Approved work instruction and any special handling record |
| Firmware | Released image, configuration, version identification and verification method | Programming result associated with the unit identity |
| Calibration | Whether calibration is required, the method, reference equipment and coefficient storage | Applicable results, conditions and approved coefficients |
| Enclosure and connections | Sensor opening, connector pinout, cable routing, seals and mounting arrangement | Assembly revision and defined final inspection results |
| Production release | Test sequence, limits, retest rules and disposition authority | Unit-level result and approval of any exception |
Make sensor handling instructions component-specific
Do not apply a generic cleaning or coating instruction to every sensing element. Pull the handling guidance for the actual part and identify which production operations need engineering review. A sensitive opening, exposed surface or removable protective feature should be called out on the assembly documentation rather than left to interpretation.
For an enclosed product, review the sequence of assembly and protection operations. Specify when a sensor is installed, what remains accessible for inspection and what must be checked after enclosure closure. If a proposed material or process has not been evaluated with the selected sensor, keep it as an approval item. This is more useful than assuming that a process used on another board transfers unchanged.
Discuss these requirements during the PCB assembly review. Include the sensor datasheet revision and relevant application notes with the package so that process decisions can be traced to the released design.
Separate calibration, programming and functional testing
These activities answer different questions. Programming loads the approved software and configuration. Calibration establishes or adjusts a defined measurement relationship under specified conditions. Functional testing checks whether the assembled unit performs the required operations. A successful programming message does not establish measurement accuracy.
Analog Devices’ AN-1464 calibration note distinguishes internal converter calibration from system calibration for the devices it covers. Use that distinction as a prompt to identify which parts of your own signal chain are included in the chosen procedure. Apply the instructions for your actual converter and sensor rather than transferring another device’s settings.
State whether coefficients belong to the individual sensor, the assembled board or the finished instrument. Define where they are stored, how they are associated with a serial number and how the test station verifies the association. Also specify what happens after a sensor replacement, firmware change or rework operation. The engineering owner should decide whether that change requires recalibration or another test.
A useful functional test plan identifies the stimulus, measurement, operating state, approved limit and stored result for each check. List uncovered failure modes explicitly. This helps a buyer understand the difference between an electrical assembly check and a product-level measurement test.
Example: an enclosed temperature-monitoring product
Consider a hypothetical monitor with a sensor board, a radio and a small enclosure. An engineering sample has been checked on an open bench, while the production product will operate with the lid installed. The handoff should require the team to decide whether the test is performed at board level, enclosure level or both, and which operating state is used during evaluation.
Turn that decision into an instruction: identify the enclosure revision, radio operating state, reference setup, stabilization criterion and acceptance document. Record any configuration that affects the measurement. This example supplies a review method, not a numerical test limit or a claim about a completed customer build.
Before releasing a sensor-board layout, use the PCB test point access review to document probe approach, component clearance and fixture support for the agreed test sequence.
Define failures and retests before the pilot build
Agree how the team will distinguish a fixture connection problem from a product failure. Preserve the initial failure record, identify any intervention and record the subsequent result. A repeated pass attempt without a documented reason can hide a setup problem and make production data difficult to interpret.
The pilot build should close questions about fixture access, handling instructions, firmware identification and record capture. Approve changes to the release package through a controlled revision. Avoid solving an issue only in an operator’s notes while leaving the next build’s documents unchanged.
What to include in your sensor PCBA inquiry
- Released PCB files, BOM, placement data and assembly drawing with matching revisions.
- Sensor part numbers, relevant handling guidance and approved alternative rules.
- Intended quantity and build stage, with any timing constraints clearly identified.
- Firmware and configuration requirements, including the verification method.
- Calibration and test scope, supplied equipment or fixtures, and any unresolved limits.
- Enclosure, cable and protection requirements where they are part of the build.
When comparing an electronic manufacturing service, ask how these responsibilities and open decisions will be captured for your project. A documented scope makes it easier to compare proposals and understand what the quoted work includes.