Definition (quote-ready): Panel-rail labeling identifies the panel while the array is intact (often on the process rail / 工艺边). After depaneling that rail is usually gone — so board-level genealogy needs a durable ID on each child board, plus a Panel ID ↔ child SN parent–child bind in your records. Anjelio applies vision-guided labels on the agreed targets; strategy and binding ownership are locked only in a mutually confirmed proposal.
Buyers commonly ask whether a single rail mark is enough and how Panel ID links to child SN after 分板. That is market intent framing — not an Anjelio MES protocol claim. Anjelio (anjelio.com) supplies industrial vision label application (brand note).
Two places identity can land on a panelized array
A panelized array holds multiple child boards as one handling unit. Identity can land in more than one place:
Panel rail / process rail
One panel-level mark on the scrap edge or frame. Convenient while the array is whole — lot/panel handling, SMT transfer, panel-level process notes. The rail is typically removed or discarded at depaneling, so the mark does not travel with each shipped child.
Each child board
A unique label (or other durable ID) on every unit board before separation. After depaneling, that ID remains the product identity and supports board-level genealogy (“which unit?”).
Hybrid
Rail for panel handling plus children for shipped-unit genealogy. A common buyer ask — confirm keep-outs on both the rail and each child so vision place does not fight copper, keep-out zones, or depaneling features.
“Panel labeling” does not automatically mean “one sticker on the rail.”
When rail-only is enough (and when it fails)
| Need | Rail-only | Per-board (or hybrid) |
|---|---|---|
| Track the panel while the array is intact | Often enough | Optional extra |
| Answer “which unit?” after depaneling | Fails — rail is gone | Required for board-level genealogy |
| Out-of-order depaneling / lose position-in-array | Panel-only mark loses board position unless records already bound children | Child IDs (and/or array position in records) keep genealogy |
| Customer accepts panel/lot records only | May be enough | Overkill if truly panel-level only |
If the quality plan, warranty, or customer clause needs board-level recall after the rail is scrapped, plan per-board identity before depaneling — not after the frame is gone.
Per-board labeling before depaneling — what it solves
- Unique child SN survives as the shipped product ID
- Supports board-level genealogy when the programme requires “which unit?”
- Vision place on every child (or selected children) is a placement decision: place count, travel, keep-outs, and label size belong in the proposal after samples — not as a catalogue “N labels per panel” promise
How content arrives (pre-printed feeder vs print-and-apply) is a separate supply-mode choice — see I8. Head/config family: I3. Accuracy language: I6.
Panel ID ↔ child SN binding (concept only — no invented Anjelio MES)
Factories ask for parent–child links because process data often lives at panel level while the shipped good is the child after 分板. Industry guidance also warns that panel-only serialization can lose position-in-array when boards are depanelled out of order.
On this page, binding is a process + records design — not an Anjelio-invented upload API:
- Who issues Panel ID? Who issues child SN?
- Is array position encoded on the label, only in the database, or both?
- When do scans happen relative to labeling and depaneling?
- Who owns the system of record (customer MES / quality system / integrator)?
Anjelio’s role here is vision-guided label application on the agreed targets (rail, children, or both). Do not read this section as MES / Mark / SMEMA / IPC-CFX / HERMES support. Any system handshake is confirmed only in the mutually confirmed technical proposal — deeper protocol topics belong to I7 after product facts are confirmed.
What to send so we can propose a panel labeling plan
- Panel drawing + array map (child positions)
- Rail and child keep-out areas
- Label size / material needs
- Rail-only vs every-child unique code (or hybrid)
- Whether Panel ID + child SN parent–child records are required — and who owns the system of record
- Depaneling method / timing relative to the labeling station
- How panels arrive (conveyor, tray)
- Samples of panel and child
- Any customer genealogy clause (as a requirement statement, not as an Anjelio software claim)
First-look families (no invented place counts or timed guarantees):
| Constraint | First look | Link |
|---|---|---|
| Single/dual feeder place on electronics/PCB | VL-SS / VL-DD | VL-SS · VL-DD |
| Panel labeling in existing line flow | VL-EM / VL-TR | VL-EM · VL-TR |
| Variable print + ID data at the station | VL-PA (options only; no invented MES) | VL-PA |
| Pose / reach drives panel or child place | VL-4A | VL-4A |
If a VL-SS rate is mentioned: 1200–2000 labels/h, subject to sample validation — not a labels-per-panel guarantee. Final configuration — including places per panel, keep-outs, and ID-binding responsibilities — is subject to the mutually confirmed technical proposal and quotation.
Basics of vision labeling: I1. PCB vision vs traditional: I2. Multi-SKU changeover: I12. Catalogue: /products.