English Views: 0 Author: Elsa Long Publish Time: 2026-11-12 Origin: Site
Buying a placement machine is a purchase order. Getting it to produce boards at the quoted rate, at the quoted accuracy, with people who can run it without calling an engineer, is a project with three separate deliverables. Most disappointing start-ups are not equipment failures. They are handovers that were never separated: the machine was powered on and called installed, a program was loaded and called programmed, and an operator watched a demo for two days and was called trained. The JUKI SMT machine installation programming training checklist below exists to keep those three claims apart and to attach evidence to each one.
The structure is deliberately not a list of tasks in the order a vendor happens to perform them. It is organized around three handovers, each with a question it must answer, a set of measurements that answer it, and a named person who signs. Between them sit the numbers that are cheap to fix before delivery and expensive afterwards, the order in which a program should be built so it can be defended in a process review, and the competence levels that decide whether a shift can run without supervision. Machines and options referenced throughout are drawn from the placement platforms this checklist is written around, and every calculation is labelled as an assumption so you can re-run it with your own figures.
A placement line becomes productive through three transitions, and each one can fail on its own. The machine can be mechanically installed and still place badly because the rail height does not match its neighbours. It can be perfectly installed and still miss its cycle time because the program was built in the wrong order. It can be installed and programmed and still stop every night shift because nobody on that shift can recover a pickup error without a phone call. Treating these as one event called "start-up" is what produces the familiar pattern of a line that is technically running in week one and still not delivering in week eight.
Splitting them has a practical cost: three acceptance conversations instead of one, and three sets of documents. It also has a practical benefit that usually pays for the extra paperwork within the first quarter. When something goes wrong later, you can tell which handover is responsible, which means you can tell whether the fix belongs to the vendor, to your process engineering team, or to your training plan. A machine that drifts out of tolerance is an installation question. A machine that runs slow is a programming question. A machine that sits idle waiting for help is a training question.
Power-on proves very little. It proves the incoming supply is within tolerance, the safety circuit closes, the axes reference, and the software boots. None of those tests tell you whether the machine is level to the tolerance the platform needs, whether the conveyor rail is coplanar with the printer upstream and the oven downstream, whether the frame is bonded to the building ground, or whether the vacuum at the nozzle tip is what the pickup monitor expects. A machine can pass power-on with a rail height error of a millimetre and then spend months pushing boards into the next machine's entrance guide.
The distinction matters because of who pays for the correction. Levelling and rail matching are cheap during installation, when the machine is on skates, the crate is still on site and the engineer is already there. The same correction six weeks later means a production stop, a re-levelling exercise, a re-check of every program that assumed a particular board datum, and often a re-qualification run. In practice, the cost ratio between doing it during installation and doing it after release is not a subtle one. It is the difference between an hour inside a planned window and a day outside one.
The same logic applies to bonding and to vacuum. A ground bond that measures a few ohms too high will not stop the machine. It will quietly sit there as a latent ESD risk on every board the line touches, and it will be discovered by an auditor rather than by production. A vacuum reading taken at the nozzle tip during installation gives you a baseline number that later readings can be compared against; without that baseline, a slow decline has no reference point and gets attributed to the nozzle, the feeder, or the operator, in that order of convenience.
Each handover answers one question and produces one signature. The mechanical handover answers whether the machine is where it should be, level, connected and safe. The program handover answers whether the machine can produce the customer's board at the required accuracy and rate, repeatably. The operator handover answers whether the people on the roster can run, recover and hand over the line without external help. Anything that does not fit one of those three questions is either a commercial matter or a maintenance matter, and should not be allowed to delay a signature.
The value of separating them is that they have different owners and different failure modes. The mechanical handover is owned by facilities and the installing engineer. The program handover is owned by process engineering. The operator handover is owned by production, with process engineering providing the standard. When a single "commissioning sign-off" covers all three, the signature usually goes to whoever is most senior in the room, and the weakest of the three is the one that gets waved through.
Handover | Question it answers | Evidence that closes it | Signs |
|---|---|---|---|
Mechanical | Is the machine placed, level, connected, bonded and safe? | Level record, rail-height record across the line, utility readings, bond resistance, safety-circuit test | Facilities lead + installing engineer |
Program | Can it build this board at the required accuracy and rate, repeatably? | First-article record, capability run with Cpk, measured cycle time against target, saved golden program | Process engineer + production lead |
Operator | Can the roster run, recover and hand over without help? | Competence matrix signed per person, certification test results, one supervised shift with no escalation | Production lead + trainer |
The table is short on purpose. A handover that needs forty lines of evidence will not be closed honestly; a handover that needs three or four lines can be closed in a single meeting and audited later without argument. If you need more detail, attach it as an annex to the handover record rather than expanding the signature page itself.
Adopt one rule before the machine ships: a checklist line is not complete because someone says it is complete. It is complete when an artifact exists that a stranger could read in six months and understand. A level record with the measurement positions and the instrument used is an artifact. A sentence saying "machine levelled" is not. A capability run with sample size, measured offsets, calculated Cpk and the board revision is an artifact. A statement that placement accuracy was verified is a marketing claim.
The rule sounds bureaucratic until the first time it is tested. Sooner or later a board will fail at a customer, the question will be whether the machine was ever capable of holding that tolerance, and the answer will be sitting in a folder or it will not. With artifacts, the conversation takes an hour. Without them, it takes a week of re-measurement, and it usually ends with a decision made on opinion. The same rule protects the vendor as much as the buyer: an engineer who can point to a signed capability record is not asked to defend a machine's reputation on the phone.
Keep the artifacts in one place, in one format, with dates. The format matters less than the discipline of a fixed location. A folder per machine, named for the asset number, containing the mechanical record, the program record, the training record and the maintenance baseline, will answer almost every question that arrives in the first year. The sections that follow describe what belongs in each of the three records, in the order the work actually happens.
Most installation delays are decided weeks before the truck arrives, in decisions nobody wrote down. The floor was poured to a general warehouse specification rather than a machine-tool one. The door the machine has to pass through is wide enough for the crate but not for the machine on skates. The compressed-air drop is at the right pressure but the wrong flow, and the dryer was sized for a workshop rather than a line. None of these are exotic problems, and all of them are cheap to solve before delivery and painful to solve afterwards.
The point of a readiness review is not to build a perfect factory. It is to find the two or three items that will stop the installation, and to fix those. A useful way to run it is to walk the route the machine will take and stop at every point where something must be true: the truck bay, the corridor, the lift or ramp, the doorway, the floor slab, the utility drops and the final position. At each point ask what the machine needs and what the building currently provides, then write down the difference and the owner of the fix. That list, not a generic checklist, is what a readiness review should produce.
Item to settle before delivery | What to confirm in writing | How to verify on site | If it is wrong |
|---|---|---|---|
Floor loading and flatness | Slab capacity at the machine footprint, flatness over the machine length | Structural drawing plus a straightedge and feeler check along the line axis | Grinding, shimming or a steel plate; days of delay |
Access route | Clear width and height at every doorway and turn, including crate dimensions | Tape measure along the actual route, not the drawing | Crate opened outside; rigging by crane or partial disassembly |
Power | Voltage, phase, frequency, breaker rating, dedicated earth | Meter at the drop under load, not at the panel | Transformer or re-cabling before first power-on |
Compressed air | Pressure at the machine inlet, flow available, dew point, filtration | Gauge and flow test at the drop with the line running | Vacuum instability, nozzle clogging, intermittent pickup errors |
Environment | Temperature band, humidity band, filtration, ESD floor | Logger for 72 hours before delivery | Paste behaviour and placement repeatability both suffer |
Two numbers govern the floor: what it can carry and how flat it is over the length of the line. Carrying capacity is the easier of the two, because it is a drawing question and the structural engineer can answer it in an afternoon. Flatness is the harder one, because a slab that looks flat under a level can still have a crown or a dip that shows up when three machines are bolted in line and the conveyor rails have to be coplanar. Check along the line axis with a straightedge, not across the room.
The access route deserves the same suspicion. Measure the narrowest doorway, the tightest turn and the lowest beam on the actual route, then compare them with the crate dimensions rather than the machine dimensions. Machines are frequently shipped in crates larger than the machine and cannot always be uncrated outside, because the site has no covered space or no crane. If the crate will not pass, the decision to uncrate outside has to be made while the truck is still scheduled, not while it is waiting at the gate.
Finally, book a window rather than a day. Rigging slips, and a rigging crew that arrives after the production floor has filled with other equipment will find the route blocked. A realistic window includes the offload, the move, the positioning, the uncrating and the removal of packaging, and it should be held free of other site work. The single most common cause of a two-day installation becoming a two-week one is not a missing part. It is a route that was clear on the day it was surveyed and occupied on the day it was needed.
Power is usually checked at the panel and assumed to be fine at the machine. Check it at the drop instead, under a representative load, and record the value. Voltage that sits at the top of the tolerance band with no load can drop below it when the oven and the compressor start together, and the resulting faults look like machine faults rather than supply faults. Record phase rotation as well; a machine that references its axes in the wrong direction after a reconnection will cost an afternoon to diagnose.
Compressed air is the utility most often sized by pressure and not by flow. Pressure is what the gauge shows when nothing is moving; flow is what the vacuum generators need when the head is picking at rate. As an illustration only, assume a machine placing 20,000 components per hour, assume each pick consumes about 0.03 litres of free air through the vacuum generator, and assume a continuous bleed of roughly 100 litres per hour across the head. That gives 600 litres per hour from picking plus 100 litres of bleed, about 0.7 cubic metres per hour for one machine, before any allowance for leakage and for other consumers on the same drop. Real figures depend on the head, the nozzle and the generator design, so measure the drop with the line running and treat the calculation as a way to size the pipe, not as a specification.
Grounding is the item that gets a visual check and no measurement. Ask for a resistance reading from the machine frame to the building earth bar, written down and dated, and repeat it at the annual audit. A bond that measures correctly on the day of installation can degrade through a painted panel, a corroded lug or a cable that was later moved during another trade's work. Without the first reading, the later one has nothing to be compared against.
Temperature and humidity affect two different things, and it helps to keep them apart. Temperature affects the machine: structures expand, and a line that is calibrated in a cold morning room and run in a warm afternoon one will show a slow drift in placement offset that has nothing to do with the head. Humidity affects the process: dry air increases static build-up and changes how solder paste behaves through the stencil. Both are worth logging for 72 hours before delivery, because the log tells you what the room actually does rather than what the specification says it should do.
ESD control is a system, not a floor tile. It includes the floor finish, the bonding of the machines, the wrist straps at the programming station, the smocks and the way boards are stored between processes. A line installed on a dissipative floor with unbonded machines is not protected; it merely looks protected. Add the bond measurement to the mechanical handover and the visual check to the weekly walk, and the system has a chance of surviving a busy quarter.
The floor finish also has a dust consequence that is easy to overlook. Sealed floors wipe clean; unsealed or damaged coatings generate dust under pallet trucks and under the castors of feeder carts, and that dust ends up on nozzle tips and in camera windows. If the floor is due for recoating, do it before the machines arrive rather than around them afterwards. It is the cheapest reliability improvement available during a start-up, and the one most often deferred because it competes with the delivery date.
Installation is a sequence, and the sequence matters more than the speed. A machine that is levelled before its neighbours are in place will need re-levelling; a machine that is powered before the bond is measured will need a shutdown to fix the bond; a feeder bank that is built before the rail height is confirmed will need to be unloaded again to move the machine. The four stages below run in the order that avoids repeated work: position and level, connect and bond, build the mechanical baseline, then power and reference. The installation stage of a JUKI SMT machine installation programming training checklist is deliberately narrow: it ends when the machine is mechanically proven, and the program work starts from that known state rather than from a hopeful one.
What installation is not is a demonstration. The temptation during these days is to accept a quick board as proof that everything works, because the engineer is present, the parts are unpacked and the customer is watching. A board produced during installation proves that the machine and the program can cooperate once, under supervision, with someone on hand to clear the error. It does not prove the mechanical handover, and it should not be used to close it.
Positioning comes first and should respect two constraints: the space the machine needs to operate, and the space a person needs to work on it. Leave enough clearance at the feeder side for a loaded cart and a technician, and enough at the back for access panels to open fully. A machine pushed against a wall to save floor space will be serviced less often than one that is not, and the cost of that shows up as unplanned stops rather than as a visible problem.
Levelling is a measurement, not a judgement. Level the machine on its own feet using the positions the manufacturer specifies, record the reading at each position, and note the instrument. Then match the conveyor rail height to the stations on either side, because a placement machine is only as good as the board's position when it arrives. Check rail height at the infeed and outfeed ends, not in the middle, and check it with a straightedge that spans the gap between machines. A rail that is 0.5 mm high at one end will tip a thin board and produce placement offsets that vary across the panel, and those offsets will be blamed on the head for weeks.
Record the result as a table, machine by machine, with the rail height at each end of each conveyor section. That single table is the most useful document produced during installation, because when a board-position problem appears in month three the first question is whether the rails have moved, and the answer takes ten minutes if a baseline exists and two days if it does not.
Connecting the utilities is straightforward work that is easy to do incompletely. Power, air, network and the interlock signals to neighbouring machines all have to arrive at the right terminal with the right rating, and each connection should be verified at the machine end rather than assumed from the drawing. Take a voltage reading at the machine inlet under load, a pressure and flow reading at the air inlet with the machine cycling, and a continuity check on the interlock chain from the line controller. Write the values on the handover sheet next to the date.
The bond check is the item that most often goes unrecorded, partly because it is nobody's obvious job. Measure resistance from the machine frame to the building earth bar through the installed bonding conductor, record the value and the instrument, and repeat the measurement at the annual audit. If the reading drifts, the cause is usually a lug that was disturbed, a panel that was repainted, or a conductor that was re-routed during later work by another trade. None of those are visible from the outside, which is exactly why the number belongs in the file.
Finish the utility stage by labelling. Every drop, isolator and network port that serves the line should carry a label that matches the drawing, and the drawing should be the version in the handover file. Unlabelled drops are how a machine gets switched off during a fault-finding exercise, and how a network cable gets unplugged by someone looking for a spare port.
The feeder bank is the part of installation that most directly sets the achievable changeover time later, so build it against the program rather than against the machine's maximum capacity. Load the feeders in the sequence the program expects, verify each one seats and locks positively, and record the position-to-part mapping. A bank built loosely will pass the first board and then produce a feeder error every time the cart is exchanged, because a feeder that is not fully seated shifts slightly under vibration and changes its pickup height.
Take the published capacity of the platform as a planning input rather than a target. As one reference point in this class, the KE-3020V and its published board, feeder and accuracy figures list a maximum board of 22 by 24 inches, components from 01005 up to 33.5 mm square, and up to 160 feeder inputs in the case of 8 mm tape on electric double tape feeders. Those numbers tell you how much of the bank a given product mix can occupy before you need a second cart, which is a changeover decision, not an installation one. Confirm the figures for the specific machine and configuration on your order rather than assuming a family resemblance.
The nozzle station and the mechanical baseline belong to the same stage. Install the nozzle set the program needs, verify each nozzle seats and is recognised by the machine, and record a first vacuum reading at the tip for each nozzle type. That reading is the baseline for every future comparison. Without it, a gradual loss of vacuum has no reference and gets diagnosed by replacement rather than by measurement.
Power-on should be a planned event with a written sequence, not the moment someone finds the breaker. Confirm the supply is within tolerance, confirm the emergency stops are accessible and functional, confirm the guards and interlocks are in place, and only then energise. Reference the axes and record whether each one references on the first attempt. A slow or failed reference at this stage usually indicates a sensor position, a contamination or a parameter issue, and it is much cheaper to resolve now than after the machine has been loaded with feeders.
Test the safety circuit deliberately. Open each guard, press each emergency stop, and confirm the machine enters a safe state and requires a deliberate reset. Confirm the light tower and the audible alert work, and confirm the interlock to the neighbouring machine behaves as designed. This is the one part of the handover where a functional test is worth more than a document, because a safety circuit that has never been tested is an assumption rather than a control.
Close the mechanical handover with the four records you now have: the level and rail-height table, the utility readings, the bond measurement and the safety test. Add the feeder and nozzle baselines as an annex. That package answers the mechanical question completely, and it lets the programming work begin from a known state rather than from a hopeful one.
A program is not finished when the machine accepts it. It is finished when someone can explain, line by line, why each part is placed in that order, with that nozzle, from that feeder position, at that speed, and what happens when the answer changes. Programs that cannot be explained are programs that get edited by trial and error, and trial and error is how a line acquires a set of undocumented variations that nobody can reproduce on a second machine.
The practical consequence is that programming deserves its own handover, separate from installation, with its own evidence. The evidence is not the program file. It is the first-article record, the capability result and the measured cycle time, all tied to a named board revision and a saved program version. This section covers the inputs, the structure and the order of work; the next section covers the proof.
Programming delays are almost always input delays wearing a technical disguise. The centroid file is in the wrong unit or the wrong origin. The BOM does not map to the placement list. The board has fiducials that the CAD data does not mention. The panel is a new array and nobody has the array drawing. Each of these costs a day if it is discovered during programming and an hour if it is discovered before.
Collect the inputs as a package and check them against each other before a single line of program is written. The centroid and the BOM should agree on reference designators; the board outline and the panel drawing should agree on dimensions and breakaway positions; the fiducial list should exist as coordinates, not as a note saying fiducials are present. Ask for the paste layer as well, because it tells you the pad geometry that the placement window has to respect, and ask which revision is authoritative.
Input | What it must contain | Common defect | How to catch it early |
|---|---|---|---|
Centroid / placement list | Reference, X, Y, rotation, side, package | Mixed units, origin not at board zero | Plot the points over the board outline before programming |
BOM | Reference to part number and package mapping | Alternate parts with different body sizes | Join BOM to centroid by reference and count the gaps |
Board and panel drawing | Outline, array, breakaway, tooling holes | Array drawing older than the board revision | Overlay drawing on the centroid plot, check the array count |
Fiducial definition | Coordinates, shape, size, clear area | Fiducials listed in prose only | Require coordinates; reject a program that guesses them |
Build the program in five layers and finish each one before starting the next. The board layer defines the panel, the array, the origin and the conveyor width. The placement layer holds the component list with reference, position, rotation and package. The feeder layer maps each part to a physical feeder position and a tape width. The nozzle layer assigns a nozzle to each package and confirms the pickup window. The mark layer defines fiducial search areas and the recognition parameters.
Doing it in this order means an error surfaces at the layer where it was introduced. If the board layer is wrong, every downstream coordinate is wrong and the mistake is obvious immediately. If the feeder layer is built before the placement layer is stable, a part change forces a re-map of positions that were already verified. The layers also map cleanly onto responsibilities: the board layer belongs to the process engineer, the feeder layer to the line lead who owns the carts, and the nozzle layer to whoever owns the consumables budget.
Head count and nozzle station layout shape how the placement layer should be split. A machine with more heads can place more parts per pass, but only if the parts are distributed so that each head has work in the same region. On a ten-head inline configuration for IC and chip placement, the difference between a balanced assignment and an unbalanced one is often larger than the difference between two machine models, because an idle head still consumes its share of the cycle. Assign by region first, then by package, then by feeder availability.
Optimization is where programs become fast or become fragile. The order that produces both speed and stability is nozzle, then feeder, then sequence. Nozzle selection sets the pickup window and therefore the maximum acceleration the machine can use without dropping parts; getting this wrong and compensating with a slower sequence produces a program that is both slow and unreliable. Feeder assignment sets the travel between pick and place positions and the number of cart exchanges; getting this wrong produces a program that is fast in simulation and slow in production because it changes carts twice a shift.
Sequence optimization comes last because it is the layer with the most freedom and the least information. Once the nozzles and feeders are fixed, the sequence is largely determined by physical constraints, and the remaining choices are about balancing heads and respecting the placement order that the process needs for other reasons. Those other reasons matter: a large connector that must be placed before a tall component, a part that must not be placed after an adhesive cure, a shield that covers fiducials. The optimizer will not know any of that, so the sequence has to be reviewed rather than accepted.
This is also where the configuration decisions made at purchase time come back. How feeder and nozzle configuration constrains the program is worth reading before the first optimization run, because a bank that is short of a tape width, or a nozzle set that is missing one bore, will force a compromise that no amount of sequence tuning can recover. Fix the configuration and the program follows; tune the program around a configuration gap and it will need re-tuning every time the mix changes.
Every board should have one program that is designated golden, saved with the board revision and the date, and treated as read-only. Production runs from the golden program. Any change is made in a copy, verified on a first article, and only then promoted to golden with a new revision number. Without that discipline, the program on the machine slowly becomes a record of every experiment anyone has tried, and the version that produced a good board last month cannot be reproduced.
The change log is the other half. One line per change: date, who, what changed, why, and what evidence supported it. A change log with twenty entries over a year is a healthy sign; it means changes were deliberate. A program with no change log and a modified timestamp from last week is a program nobody can defend. Store both the golden file and the log in the handover folder for the machine, so the program record sits next to the mechanical record and the training record.
Back up the golden program outside the machine as well. Machine-resident storage is convenient and is not a backup. A copy on the plant network plus a copy in the handover folder covers the two realistic failure modes: a controller that loses its data, and a program that gets overwritten by someone who was sure they were editing a copy.
Proving a program means answering three questions with numbers: does it place correctly, does it place repeatably, and does it place fast enough. Each question has a different measurement and a different failure mode, and merging them into a single "trial run" is how programs get released on the strength of one good board. A single board can be correct by luck. Ten boards can be correct and still not repeatable. Repeatable boards can still miss the quoted rate by thirty percent because the program spends its time travelling between feeders. This stage is also where a JUKI SMT machine installation programming training checklist earns its keep, because proving is the only stage that produces measurements rather than opinions.
The three measurements below are cheap to run and give you a defensible handover. Run them in order, because a capability run on a program that has not passed a first article is measuring the wrong thing, and a cycle-time measurement on a program that is not yet repeatable is measuring a number that will change.
The first article is an inspection exercise, not a production run. Build a small number of boards — enough to see whether the program is stable, typically three to five — and inspect every placement on every board, not a sample. Check presence, orientation, position within the pad window, and any part that the program placed at an unexpected rotation. Inspect before reflow as well as after, because reflow can pull a slightly misplaced part into position and hide a program error that will reappear on a denser board.
Record the result by reference designator, with the measured offset where you can measure it and a pass or fail where you cannot. The point of recording per reference is traceability: when a defect appears in production, the first-article record tells you whether that reference was ever correct. A first article recorded as "visually acceptable" answers nothing six weeks later.
Include the awkward parts deliberately. The smallest package on the board, the largest, the tallest, the one with the tightest pad geometry and the one nearest a fiducial all deserve a specific look, because those are the placements where a program built from nominal data usually fails. If the board has a part that the machine can only place with a special nozzle or at reduced speed, note it on the first-article record so that the exception is documented rather than rediscovered every time the program is copied.
Capability is a statistical claim, so it needs a sample. Measure the placement offset of one or more critical references across a run of boards — thirty placements of the same reference is a workable minimum for an indicative result, and more if the process is marginal. Measure X and Y separately, because a machine can be centred in one axis and biased in the other, and a combined figure hides that. Then calculate the capability index against the pad window the process actually needs, not against the machine's specification.
As an illustration only, assume a placement window of plus or minus 0.10 mm around nominal for a small chip, assume the measured mean offset is 0.010 mm and the standard deviation is 0.025 mm. The distance to the nearer limit is 0.090 mm, and three standard deviations is 0.075 mm, so the index is 1.20. That number is a statement about the combination of machine, program, board support and measurement method. It is not a statement about the machine alone, which is why it belongs in the program handover rather than in the installation record. The method for characterising placement performance is standardised, and referencing IPC-9850 in the acceptance document tells everyone which definition is being used.
Measurement | How to run it | Accept when | If it fails |
|---|---|---|---|
First article | 3–5 boards, every placement inspected before and after reflow | No placement outside the pad window, no orientation error | Fix the program layer that caused it; do not adjust the machine |
Placement offset | 30 placements of a critical reference, X and Y separately | Mean near zero, spread inside the window, index at or above 1.33 | Check support, nozzle, feeder height before touching calibration |
Cycle time | Time 20 consecutive boards from load to unload | At or below the quoted rate with a stated allowance | Re-optimise feeder assignment and head balance |
Repeatability | Re-measure offsets at the end of a shift | No systematic drift from the start-of-shift result | Thermal or mechanical cause; investigate before release |
Cycle time is where expectations and reality separate most often, and almost always for a reason that was knowable in advance. The quoted rate is an optimum figure measured under defined conditions on a defined mix. Your board is not that mix. As an illustration, assume a quotation states an optimum rate of 40,000 components per hour, assume your board carries 250 placements, and assume the measured time from load to unload is 62 seconds. The effective rate is 250 placements times 3,600 seconds divided by 62 seconds, which is about 14,500 components per hour. That is not a machine failure; it is the difference between an optimum figure and a real board with real travel, real fiducial reads and real board handling.
Do the arithmetic before the purchase, not after the installation. Take the board's placement count, add the handling and fiducial overhead you expect, apply a realistic efficiency factor to the quoted rate, and see whether the resulting number meets the capacity you need. If it does not, the answer is a different configuration or a second machine, and it is far cheaper to discover that in a spreadsheet. For lines where throughput is the deciding constraint, the comparison in the throughput comparison that sets the cycle-time target shows how much of the difference comes from the platform and how much from the board.
Measure cycle time over a run, not over a board. Twenty consecutive boards from load to unload includes the handling and the occasional retry, which is what production actually experiences. A single fast board tells you the machine can do it; twenty boards tell you the line can.
A failed proving run is informative if you read it in the right order. Start with the distribution of the errors, not the count. Errors clustered on one head point to a nozzle or a head-specific parameter. Errors clustered in one region of the board point to support, clamping or board flatness. Errors spread across all references with a consistent direction point to a datum or a fiducial offset. Errors that appear only on the smallest parts point to the pickup window or the nozzle bore. Each pattern has a different owner, and none of them is fixed by recalibrating the machine.
Recalibration is the most over-used response to a proving failure, because it is the response that requires the least thinking. If the mechanical handover was done and the baselines recorded, you already know whether the machine moved. If it did not move, recalibrating it will not fix a program that assigns the wrong nozzle, and it will destroy the baseline you paid to establish.
Write the diagnosis down before the fix. Two lines — what the pattern was and what it indicated — turn a bad afternoon into a reusable lesson. That note belongs in the change log, and the next program written for a similar board starts from it instead of from scratch.
Training is the handover with the weakest evidence in most factories, because it is the one where success is hardest to measure and easiest to claim. An operator who has watched a demonstration can start a program and stop a machine. An operator who can run a shift alone can also recover a pickup error without scrapping the board, recognise the difference between a feeder fault and a nozzle fault, hand over a machine state accurately at shift change, and know which problems to escalate and which to solve. The gap between those two people is where most night-shift losses live.
The way to close it is to define the levels, test for them, and put a name against each level on each machine. That sounds like administration, and it is, but it converts training from an event into a state that can be audited. It also protects the trainer, who can otherwise be blamed for a competence gap that was never defined in the first place. On a JUKI SMT machine installation programming training checklist, training is the last handover and the only one that cannot be closed in a meeting room.
Four levels are enough to run a line and few enough to remember. Level one is supervised operation: the person can start and stop a program under observation. Level two is independent operation: the person can run a shift, perform the daily checks and hand over the machine state. Level three is recovery: the person can clear the common faults, replace a nozzle or a feeder, and re-qualify the machine with a first article. Level four is programming and setup: the person can build and optimize a program and change a feeder configuration.
Post the matrix where the roster is posted, with names against levels against machines. Two rules make it useful. First, no one operates a machine at a level they have not been signed off for, regardless of seniority. Second, at least two people per shift must hold level three on every machine, because a single level-three operator is a single point of failure for the whole shift. The matrix makes both rules visible, which is most of the work of enforcing them.
Level | Can do without help | Evidence | Minimum coverage per shift |
|---|---|---|---|
1 — Supervised | Start, stop, load and unload under observation | Signed observation by trainer | All operators |
2 — Independent | Run a shift, daily checks, shift handover | Two supervised shifts with no escalation | All operators on the roster |
3 — Recovery | Clear common faults, swap nozzle or feeder, run a first article | Practical test on the actual machine | Two people per shift |
4 — Setup | Build and optimize a program, change feeder configuration | Program built and accepted by process engineering | One person per site, plus a deputy |
Week one is about the machine and the board. The operator should see the whole line running, learn where the safety devices are and how to test them, practise loading and unloading, and watch a full program run from start to finish with the trainer narrating what the machine is doing. The deliverable at the end of week one is level one: the person can start and stop the program and knows what normal looks like on the display.
Week two is about faults and judgement. Introduce the three or four faults that account for most stops on this board — a pickup error, a feeder index error, a fiducial recognition failure, a board transfer error — and let the operator clear each one with the trainer watching. The deliverable is level two, and it should be tested on a shift where the trainer is present but not intervening. Week four is about recovery and independence: nozzle and feeder changes, the first-article procedure, and a full shift with no escalation, which is where level three is earned.
Product-specific training belongs inside that sequence, not before it. A board with unusual geometry or a platform with a different head arrangement needs its own practice: a four-head platform used for LED driver boards, for example, will have a different feeder loading pattern and a different set of awkward parts than a high-density logic board. Training on the actual product mix is what turns general competence into shift performance; training on a demonstration board produces people who are competent at the demonstration.
A certification test should be practical, short and repeatable. Give the operator a machine in a known state and a task list: load this program, run three boards, clear the fault I introduce, perform the daily check, and hand the machine over to me in writing. Score on completion and on whether the machine is left in a correct state, not on speed. A test that can be passed by watching someone else do it is not a test.
A fail is information, not a verdict. Most fails trace to one of three causes: a level was signed off without the practice behind it, a procedure was never written down so the operator invented one, or the test used a fault the operator had never seen. Each cause has a different fix, and none of them is "train harder". Record the cause next to the result, because a pattern of the same cause across several people is a training-material problem rather than a people problem.
Re-certify on a fixed interval and after any significant change: a new board, a new platform, a major software update, or a long absence from the machine. An interval of twelve months is common; a change-triggered re-certification matters more than the calendar one, because competence decays fastest right after the process it was built on has changed.
Most lines have one person who knows everything about the machine, and that person is a risk. When they are on leave, the line runs at reduced capability; when they leave, the knowledge leaves with them. The way out is not to document everything — documentation written by an expert for an expert rarely transfers — but to create a second and third person who can teach the specific procedures, and to make teaching part of their role rather than an extra task.
A workable arrangement is one trainer per shift plus a deputy, each holding level four on at least one machine and level three on all of them, with a monthly session where they run the training for new operators together. The session doubles as a check on the material: when two trainers teach the same procedure and disagree, the procedure is ambiguous and gets fixed.
Record who trained whom. A training record that shows only that a course happened is not useful; one that shows which person signed off which level on which machine, and when, is what an audit asks for and what a new production manager needs in the first week.
The three handovers produce a set of documents, and the documents are worth nothing if they are scattered across three laptops and an email thread. Assemble them into one file per machine, physical or digital, and make it the reference for everything that happens afterwards. This is the difference between a start-up that can be audited and a start-up that has to be remembered. It is also the difference between a warranty conversation that takes one meeting and one that takes a month.
The file should be assembled during installation, not afterwards. Documents collected after the engineer has left are always partial, because the person who could answer the questions has gone. Keep a folder open on the first day and put things in it as they are produced, and the file assembles itself. The alternative — reconstructing it in month three — costs far more than the discipline of doing it now. Understanding which model you are installing and why is the prerequisite for all of this, and the selection sequence that decides which model you are installing is worth keeping in the same folder as the justification for the configuration that was ordered.
Ask for the documentation package as a deliverable in the order, not as a favour at the end. The core set is predictable: the machine manual including the maintenance schedule and the error-code list, the electrical and pneumatic drawings as installed, the parameter backup or a documented procedure to produce one, the calibration certificate or the as-shipped measurement record, the spare-parts list with part numbers, and the software version details with the procedure for restoring them.
Two items on that list are usually missing and are the two that matter most later. The parameter backup is the one that saves a day when a controller loses its data, and it is the one nobody thinks to request until they need it. The as-installed drawings are the ones that show what was actually wired rather than what was designed, and they are the only reliable reference when a machine is moved or a line is extended.
Add the records you produced: the level and rail-height table, the utility readings, the bond measurement, the feeder and nozzle baselines, the first-article and capability results, and the training matrix. The complete file then answers both questions an auditor asks — what the vendor supplied, and what you verified — without a search.
Thirty days after release, re-measure a short list and compare it with the installation record. Re-check the rail heights at both ends of each conveyor section, the bond resistance, the vacuum reading at one nozzle of each type, and the placement offset on the same critical reference used in the capability run. Four measurements, one afternoon. If any of them has moved, you have found a drift while it is still cheap to correct, and you have found it with a baseline to compare against rather than an opinion.
The audit should be attended by production, process engineering and maintenance, and it should be short. Its output is a decision per measurement: unchanged, drifting within tolerance, or out of tolerance with an owner and a date. A drift inside tolerance is not a pass; it is a trend to watch at the next audit, and recording it as such is what turns the audit into a maintenance input instead of a formality.
This is also the point to confirm that the maintenance work has actually started, because the preventive schedule for a new machine should begin on the day it enters production rather than on the day the first fault appears. If the line has been running for thirty days with no recorded checks, the audit will show it in the baselines, and the correction is a schedule rather than a repair. The structure for that schedule, by failure timescale rather than by subsystem, is set out in the preventive maintenance schedule that should start on day one, and it can be adopted as it stands if the site has nothing in place.
Most of the problems described in this guide are avoidable with four clauses in the purchase order. The first defines the handover evidence: a named list of documents and measurements that must be delivered before final acceptance, with the acceptance payment tied to it. The second defines the acceptance run: which board, which sample size, which measurement method and which threshold, agreed before shipment so that nobody negotiates it on the day.
The third defines training as a deliverable with a test: number of people, number of days, the syllabus in outline, and a practical assessment per person with the results handed over in writing. The fourth defines the support response after handover: how to reach support, what response time applies, and what happens if a fault cannot be resolved remotely. These clauses are not adversarial; a vendor that expects to deliver a working line will accept them without argument, and one that resists them has told you something useful before the machine ships.
Write the thresholds as numbers and the deliverables as artifacts, never as adjectives. "Adequate training" is not a clause; "four operators certified at level three on the installed machine, with written assessment results" is. The difference in enforceability is total, and it costs nothing to specify at the order stage.
Review your start-up plan before the machine ships
Most of the cost in a placement line start-up is decided before the crate is opened: the site numbers, the acceptance criteria, the training scope and the evidence that closes each handover. If any of those are still open questions on your project, they are worth resolving now rather than during the installation window.
Send us the board data, the target rate and the current line layout, and we will review the readiness list, the program inputs and the acceptance criteria against the platform you are installing. If you would rather start from the equipment side, begin with the platforms on our placement range and work back to the checklist from there.
We can also compare your acceptance thresholds with what the platform is specified to hold, so that the numbers written into the order and the numbers measured during the acceptance run are the same numbers. If you already have a JUKI SMT machine installation programming training checklist in use, send it as it stands: reviewing a document you already run is faster than starting from an empty page, and it keeps whatever your team has learned on previous start-ups inside the plan.
These are the questions that come up while a start-up plan is being written, usually from a process engineer who has inherited a delivery date and a checklist nobody has read since the order was placed. They are answered in the order the decisions have to be made: how long the work takes, what can be done before the machine arrives, what to do when a second machine or a used machine joins the line, and what to do when a measurement misses its target. Where the answer depends on the board, the platform or the site, the answer says so and gives the measurement that settles it rather than a number borrowed from another factory. Anything that reads like a performance promise has been left out deliberately. What follows can tell you how to decide and what evidence to demand; it cannot tell you what your line will achieve.
Separate the three handovers and the estimate becomes manageable. Mechanical installation for a single machine is usually a matter of days once the machine is on the floor: positioning, levelling, rail matching, utilities and the safety test. Programming and proving depend almost entirely on whether the data package was complete, and run from two days for a simple board with clean data to two weeks for a dense board with a new panel array and several special parts. Training is the long pole, because competence takes weeks rather than days.
The practical planning rule is to schedule mechanical and program work back to back with the same engineer present, then allow a separate window of two to four weeks for training to reach independent operation. Compressing training into the installation window is the most common cause of a line that is released on schedule and still cannot run a night shift three months later.
Yes, and you should. Most placement software allows a program to be built and optimized on an office computer from the centroid file, the BOM and the board drawing, then transferred once the machine is installed. That removes days from the installation window and, more importantly, forces the data package to be checked while there is still time to fix it.
The limitation is that an offline program cannot know the physical feeder bank, the actual nozzle set or the machine-specific calibration. Build the board and placement layers offline, leave the feeder and nozzle layers to be confirmed on the machine, and treat the offline sequence as a draft. A program that arrives fully optimized from an office is usually a program that assumed a feeder layout the line does not have.
Retraining is required, but it is shorter than the first round. The board and placement concepts transfer, so a level-three operator on one model usually reaches level two on the new machine within days and level three after a practical test on the specific fault set. What does not transfer is the interface, the fault codes, the feeder seating arrangement and the location of the maintenance points.
Plan for a competence matrix per machine rather than per person, and record levels against each machine. The mistake is to assume that a level-four operator on the existing platform is automatically cleared to set up the new one; the setup knowledge is machine-specific even when the concepts are not. A short, machine-specific bridging session plus a practical test closes the gap reliably.
Four mechanical artifacts and three program artifacts will carry almost any acceptance conversation. Mechanically: the level and rail-height record, the utility readings taken at the machine, the bond resistance measurement, and the safety-circuit test result. For the program: the first-article inspection record per reference, the capability result with sample size and method, and the measured cycle time over a run rather than a single board.
Add the training matrix per person and per machine, and the package is complete. If a supplier cannot produce those items, the line is not ready to be accepted regardless of how well the demonstration board looked. The test is not the volume of paperwork but whether a stranger could read the file in six months and know what was verified and what was not.
Cover the roster, then add depth. Every operator who will run the machine needs level two, because level two is what a normal shift requires. Beyond that, at least two people per shift need level three so that fault recovery does not depend on one individual, and at least one person on site needs level four with a named deputy.
The arithmetic is driven by absence, not by headcount. If a shift has three operators and only one holds level three, then any leave, sickness or training day removes recovery capability from that shift entirely. Count the people who can recover a fault, not the people who can press start, and staff the second number.
The structure holds, but the emphasis shifts from installation to condition. A used machine needs the mechanical handover to include a wear assessment — guides, belts, bearings, nozzle condition, feeder index accuracy — and it needs the calibration baseline to be established rather than confirmed, because there may be no as-shipped record to compare against. The program handover is largely the same once the machine is mechanically sound.
The one item that changes most is the parameter backup. A new machine arrives with documented parameters; a used machine may arrive with a configuration that reflects the previous owner's product mix. Capture the full parameter set before changing anything, and keep it separate from your own configuration, so that a mistaken edit can be reversed. A JUKI SMT machine installation programming training checklist written for new equipment should have a condition-assessment annex added for a used one, not a different document.
Read the error distribution before touching the machine. Errors on one head point to a nozzle or head parameter; errors in one region of the board point to support or clamping; a consistent directional bias points to a datum or fiducial offset; errors only on the smallest parts point to the pickup window. Each of those is a different fix, and none of them is recalibration.
If the pattern genuinely indicates a machine condition, recalibrate — but do it against the baseline recorded during installation, so you know what changed. Then re-run the same capability test with the same sample size and method, and record the second result next to the first. A failed first run that is diagnosed and closed with evidence is a normal part of a start-up; a failed run that is fixed by adjusting until the board looks right is a defect that will return with the next product.
