Skip to main content
GullySystem
A practical guide

Why the BOM and the released revision keep drifting apart

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

The BOM drifts from the released revision when edits happen in one file while the ECO, the traveler and the stock location live elsewhere. Fix it with a single released record, an ECO that changes it, a traveler printed from it, and a check at kitting and line start.

How the drift starts

It rarely starts with a big mistake. A buyer swaps a resistor for an equivalent because the original is out of stock, and the edit lands in the working Excel file. The ECO follows late, or never.

Meanwhile the traveler on the floor still lists the old part, stores picks what that traveler says, and the line loads whatever stores handed over without asking why.

Three documents now describe three different boards. The first person to notice is usually an operator holding a reel that does not match the pick list, after the kit is built. A quiet edit becomes a stopped line.

The usual gaps between BOM, ECO and traveler

Most houses hold four copies. There is the customer file, the internal costed file, the one inside the pick and place program, and the one printed on the traveler. Each changes on its own schedule. Nobody owns the set. That is the root cause.

ECOs add a second layer. An ECO may be approved but not yet applied, or applied to the BOM but not to open work orders, so boards already in kitting get caught first.

Reference designators cause special trouble. A line reading C12 to C18 in one file and seven separate lines in another will not compare cleanly, so a manual check misses it.

  • Customer BOM revision different from the internal one
  • ECO approved but not applied to open work orders
  • Pick and place program built from an older file
  • Traveler printed days before the ECO
  • Alternate part used on the floor but never recorded

Find where your copies disagree

Pick one active job. Pull the customer BOM, the internal BOM, the program file and the traveler, then compare them line by line for part number, quantity and reference designators.

Write down every difference. Ask who changed it and when, because the pattern shows which handoff is leaking, and it is often the step between engineering and purchasing. Start at that handoff.

Do this for three jobs. One job can be an accident while three show a habit, and the feeder setup file of the pick and place machine often carries the oldest copy. Nobody opens it until loading day.

Control points that stop the wrong revision

Keep one released record per assembly, with a revision letter and a state of draft, released or obsolete, and let only released revisions attach to a work order. Drafts stay out of the shop.

Make the ECO the only way to change a released BOM, and have it list the affected work orders and the stock on hand of the old part. Someone chooses use up, rework or scrap.

Print the traveler from the work order, never from a loose file, then check again when stores kits the job and when the line starts the run.

  • Revision letter printed on traveler and kit label
  • Kitting scan that rejects a part not on the revision
  • Line start check of program version against the BOM
  • ECO list of open work orders and stock on hand
  • First article sign off against the released revision

Make the checks routine

Software helps because it can refuse. A system that lets a work order use only a released revision removes a whole class of errors that training alone never will.

Even without software, a weekly review works.

Name one owner for the released record. Engineering usually fits best, while purchasing may propose alternates but never publish them, and that single owner answers when two documents disagree. This week, take your three most active jobs and list the revision on each of the four documents, starting with the job nearest to its ship date.

BOM revision cross-check sheet

Each active job takes one line, with columns for customer BOM revision, internal BOM revision, program version, traveler revision and latest approved ECO number. A final column records match or mismatch, the owner of the fix and the date it closed, so open gaps stay visible to everyone. A box underneath holds the review date.

Open a blank worksheet to print

Questions owners ask

What is an ECO in PCB assembly?

An engineering change order is the record that approves a change to a design or BOM, and it states what changes, why, and which revision results. It lists the open jobs touched.

Can a customer change a BOM mid-run?

They can ask, but treat the request as an ECO, check boards already built and parts already kitted, and decide the cut-in point in writing. Do not just edit the file. Ask the customer to confirm the new revision by email, then file that message with the ECO so the approval can be found later.

Should alternates change the revision?

A swap listed as an approved alternate on the BOM line needs no new revision, but a swap outside that list needs an ECO and a new revision. Keep a dated note of who approved each alternate and whether the customer signed off too, so audits find the answer quickly.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements