Skip to main content
GullySystem
Requirements checklist

What to ask for when choosing software for pCB manufacturers.

A checklist built from how pCB manufacturers work, to print or save as a PDF and bring to any supplier meeting.

Share your requirements

What the software should cover

Tick each one that matters to your business.

  • Order and file revision register
  • Engineering query tracker
  • Stack-up and panel planning
  • Lot travellers by process step
  • Yield and scrap by step
  • Electrical test results
  • Certificates and shipment

Roles that need their own access

Who logs in, and what each person may see or change.

  • For CAM engineers
  • For the planner
  • For process leads
  • For quality
  • For the owner

Reports to ask for

Ask to see each one with your own sample data.

  • Yield by process step, by week and by board type
  • Orders waiting on engineering queries
  • Scrap reasons for drilling, plating and etching
  • Lots affected by a given bath change or press load
  • Electrical test failures by lot and customer
  • Laminate and prepreg stock against open lots
  • Quoted against actual panel utilisation

Systems it may need to connect to

Note which ones you already run.

  • Email
  • Test equipment result files
  • Accounting export
  • SMS
  • WhatsApp

Questions for any vendor

Put these to every supplier you are comparing.

  • Does it replace our CAM software?
  • Can one panel lot carry boards of different part numbers?
  • How are impedance coupons handled?
  • Can the buyer see where a lot is?
  • What if a lot is split at a step?
  • Do operators need a PC at each station?
  • How long does moving our order history take?
  • How is the cost worked out?
  • How long before engineering and the planner work in it?
  • What do we prepare beforehand?

Where the work usually breaks today

Circle the ones you recognise. They set the order of the project.

  • The wrong Gerber revision gets imaged
  • Engineering queries wait in email
  • Yield is known only at the end
  • Chemical bath changes are not tied to lots
  • Customer certificates are typed by hand

Check the difficult cases before choosing software.

Use examples from your own records to test the workflows that matter in your business.

Order and file revision register

Which version applies to work that has already started?

Use a revised example from “Order and file revision register” during a scoped walkthrough. Identify work still using the earlier version before deciding which jobs should change.

Background reading: Odoo: controlled product changes

Stack-up and panel planning

Which observation would change the proposed scope?

For “Stack-up and panel planning”, observe someone completing the task with a representative example. Record where they stop, ask another person or re-enter information, then choose the smallest change whose result the team can verify.

Background reading: GOV.UK: researching user needs

Prefer to talk it through? See the pCB manufacturers page.