A cleaning cycle can finish without anything being released. The machine says the program ended; nobody has said the part is fit to go back on the line. The gap between those two sentences is a record, and most cleaning stations do not produce one. This article lists the six records a release decision needs and the data path that has to carry them.
The argument is not abstract. The count comes from a document check run on 26 October 2026: every technical table on the 22 datasheets at chuangqitech.com, which are the sheets a buyer receives before an order, was read and its field names tallied. Four sheets name a control system, each as a touchscreen with a PLC. Exactly one of the 22 publishes a communication row — the substrate dust-removal unit, which lists MES integration and SEMI I/O — and that machine is not a wet-wash, stencil or nozzle station. For the stations that clean those objects, the documents stop at the control panel. Verification exists in the paperwork — our factory inspection includes spray-pressure calibration, uniformity testing of the drying temperature, a continuous 72-hour run, and an ionic cleanliness test board — but it sits at build acceptance, not at the cycle that just finished. That is the gap the trade-show floor is now selling against.
Key takeaways
- “Washed” describes a process state. “Released” is a decision with a name on it.
- One of 22 datasheets lists a data-interface row; it is not a washer.
- Six records carry a release: object, program, criterion, result, decision, signer.
- If the station cannot export the cycle, the operator becomes the only data path.
- One stencil, one record, one signature per cycle beats a monthly summary.
What “released” has to mean on a cleaning station
Define the word before you buy anything. A release is a statement that a specific object completed a specific program and met a specific criterion, made by a person who is accountable for it. Four elements, all present or none of them count.
This is where the show-floor language and the shop-floor language diverge. Integrating inspection, sorting and handling into one station changes who can see the result. It does not, by itself, change who signs. A camera that photographs a stencil and a flow sensor that reads a nozzle are instruments; a release is a decision made on their output by someone whose name is attached to it.
The practical consequence is simple. If your station can produce a pass or fail but not a record, you have verification without traceability. If it can produce a record but nobody signs it, you have traceability without accountability.
Six records a release decision needs
The list is deliberately short. Each row is a thing you can hold, print or export today, not a system you have to buy.
| Record | Signed by | What it proves |
|---|---|---|
| Object ID | Operator | Which stencil, nozzle set or carrier was cleaned |
| Program and cycle | Operator | Which recipe ran, and for how long |
| Criterion | Process engineer | The limit the result will be judged against |
| Result | Operator or inspector | The measured value or inspection outcome |
| Decision | Shift lead | Release, re-clean, or hold |
| Exception note | Whoever found it | What was odd, and what was done about it |
Structure is a recommendation from CHUANGQI process work, not a compliance requirement. Your customer drawing, workmanship standard or quality system sets what is mandatory.
Two of the six are usually missing. The criterion is missing because nobody wrote down what “clean enough” means for a stencil aperture or a nozzle bore, so the inspector improvises under a light. The exception note is missing because the operator who spotted the anomaly had nowhere to put it, and the anomaly disappeared with the shift.
The data path: what the station must be able to hand over
Ask four questions before you accept a station design. They are technical questions, and each has a checkable answer.
- What is the export format, and does it carry the object ID? A CSV of cycle counts is not a record. A row that ties one object to one program is.
- Where does the criterion live? If the limit is typed into a spreadsheet outside the machine, the machine cannot judge, and every release depends on someone remembering the number.
- What happens to a failed cycle? A station that logs passes and discards failures produces a perfect record of a process nobody can audit.
- Who can edit a stored record? Read-only after signing, or editable by anyone with the supervisor code — this decides whether the record survives an audit.
The audit result above is why these questions belong in the RFQ rather than in a later integration project. The documents buyers read today describe the machine as a mechanical unit: conveyor speed, tank volume, spray pressure, power. CQ-C9610 lists a belt range of 0–1500 mm/min and DI water specified above 15 MΩ; CQ-C743 lists 0.45 µm filtration and a drying temperature up to 99 °C. Both are specifications of what the hardware does. Neither answers what the station will tell you afterwards: the interface row exists on exactly one datasheet, and that sheet belongs to a dry dust-removal unit.
There is a second, quieter cost. When the station cannot export, the operator is the data path. Every release depends on that person’s attention, every audit depends on that person’s memory, and every shift change is a small data loss. A station that writes a record converts a personal habit into a property of the process.
Where a record-based release does not fit
Not suitable for a single-operator cell with one product. If one person cleans one stencil type all day, six fields per cycle add work and prove what everyone already knows. A daily line check is proportionate there.
Not suitable where the criterion is genuinely subjective. Appearance-based release on a cosmetic surface cannot be automated into a number without inventing a threshold. In that case keep the criterion human, but still write down who decided and on what basis.
Not a substitute for process validation. A release record proves one cycle. Proving the process is capable over a product family is a different exercise, with a different sampling plan, and one does not replace the other.
Do I need a full MES connection to release a cleaned stencil?
No. A signed paper traveller with the six fields above satisfies the decision. The MES matters when you need to search history across thousands of cycles, not when you need to release one stencil tonight.
What is the difference between cleaning verification and process validation?
Verification checks one object against one criterion at one moment. Validation shows the process reliably meets that criterion across products, shifts and machines. Verification is a gate; validation is a study.
How long should cleaning records be kept?
Your customer contract and quality system set the period; we cannot set it for you. Practically, keep records at least as long as the parts they cover can still be found in the field.
Can an operator sign a release without a test?
Only where the criterion is visual and the operator is trained to that criterion. Where a measured limit applies, the release needs the measurement, and the measurement needs a device that is checked on a schedule.
What should I ask a supplier about data output?
Ask for one real export file from a machine in the field, not a screenshot of a dashboard. The file shows whether object IDs, criteria and results are actually captured, or only cycle counters.
Machine figures in this article are taken from chuangqitech.com product pages read on 26 October 2026. The field counts describe what those 22 published documents contain, not what any machine can do internally.
Writing the release criteria for a stencil or nozzle station? Send the object list and the criterion you use today through the cleaning application form — a quote is with you inside 24 hours. Start here: automatic nozzle cleaning machine (CQ-C716). For the line-level version of this argument, read PCBA cleaning line process validation; for the stencil side, stencil cleaning best practices.