An automation review is most useful when the discussion starts with the real production situation rather than an assumed machine configuration. The aim is to give the engineering team enough context to identify questions, risks, and the next evidence needed for evaluation.

Start with the PCB and components

Please prepare clear images of the PCB from both sides, including the component areas that are relevant to the proposed process. Component photos are equally important, especially where the lead direction, body shape, packaging, or presentation may affect handling.

Where available, share a component list that identifies the relevant parts, their quantities per board, and their package or supply format. A complete BOM is not required for an initial discussion, but the list should be accurate enough to guide the questions that follow.

Describe the current process

An engineering review also needs a short view of how the work is performed today. Useful details include:

  • The current insertion, assembly, inspection, and soldering steps.
  • The target production capacity, such as boards per shift or per day.
  • The automation pain point: labour availability, consistency, bottlenecks, quality concerns, or another constraint.
  • The required schedule, including any target date for a decision, sample review, or production start.
  • Whether representative PCB assemblies and components are available as samples for evaluation.

Photos or a short process video can clarify a point quickly, but they should be paired with the production context. For example, target capacity without the current process gives only part of the picture.

Keep the first review evidence-led

Early information helps an engineering team decide what must be checked next. It does not by itself confirm that a particular machine configuration is feasible. Feeder approach, component handling, tooling, process integration, and sample results may all require further review.

When the information is ready, send it as one clearly labelled package. This creates a more focused technical discussion and makes it easier to agree on the next evaluation step.