Line integration

Custom integrated automation: one line, not a row of machines

Most end-of-line problems aren't inside a machine. They're between machines — at the handoffs, the rate mismatches and the separate screens. Odecopack integrates case packers, palletizers, robot cells and the equipment you already own into one line that starts, stops and recovers as a single system.

Control panel integrating a packaging line on one PLC architecture
Machines
Case packers and palletizers we build
Robotics
FANUC Authorized System Integrator
Controls
EtherNet/IP · Safety over EtherCAT
Accountability
One contract, concept to commissioning
The short answer

What integrated automation means

Integrated automation is what turns several automated machines into one automated line. Each machine can work perfectly on its own test and the line can still lose an hour a shift — because nobody engineered what happens when product passes from one machine to the next, when one stops, or when the line changes format.

Custom industrial automation projects usually start with a single machine. The good ones are planned so the second and third machines join the first under the same controls, the same safety scheme and the same idea of how the line should behave.

For engineering a single custom cell, see custom automation. This page is about what happens between cells.

Between the machines

Six places an integrated line fails

None of them show up in a single machine's spec sheet. All of them show up in your line's output.

The handoffs

Product changes hands between machines — case packer to conveyor, conveyor to palletizer. Each transfer is a place for product to jam, tip or arrive out of position.

We design each transfer as part of the system: product orientation, spacing and pickup position agreed between the machine that releases it and the machine that receives it.

Mismatched rates

Machines rarely run at exactly the same rate, and they never stop at the same moment. Without room to absorb the difference, one short stop becomes a stopped line.

Rates are balanced across the line at scoping, with accumulation sized so a brief stop downstream does not immediately starve or back up the machines around it.

Controls islands

Every machine arrives with its own PLC and its own screen. Nobody sees the line as one thing, and diagnosing a stoppage means walking between panels.

The machines are tied into one controls architecture over the protocols your plant already runs, such as EtherNet/IP and Safety over EtherCAT, so the line starts, stops and reports as a unit.

Fault recovery

When one machine faults, what do the others do? Undefined behavior at a fault is how a two-minute stop becomes a twenty-minute restart.

Stop, hold and restart behavior is defined for the whole line, so a fault in one cell puts its neighbors into a known state instead of an improvised one.

Safety between machines

Each machine may be guarded on its own, while the gaps between them — where people clear jams — are nobody's responsibility.

Safety is assessed across the line, including access points between machines, rather than accepted as the sum of each machine's own guarding.

Changeover as a line event

Switching SKUs means every machine on the line changing over. Done one machine at a time, the line spends longer changing than running.

Changeover is planned for the line as a whole, so the machines switch formats in a coordinated sequence rather than each on its own schedule.

What goes on the line

The machines we integrate

We build the case packers and palletizers ourselves, integrate the robots as a FANUC Authorized System Integrator, and bring your existing equipment into the same scheme.

T-BOT Cartesian Case Packer loading cases
Case packing
Robotic palletizer stacking cases at the end of the line
Palletizing
Control panel with HMI tying the line together
One controls architecture

Case packing

Our T-BOT Cartesian Case Packer, or a robotic case packing cell where the product needs one.

T-BOT case packer

Palletizing

Our gantry palletizer for moderate rates and case weights, or a robotic palletizer for faster, heavier lines.

Palletizers

Robot cells

FANUC robot cells for pick and place, kitting or machine tending, engineered with their own tooling and guarding.

Robotic integration

Equipment you already own

Machines already on your floor, brought into the same controls and safety scheme through retrofits and upgrades.

Retrofits and upgrades
In stages, not all at once

How a line gets integrated

You rarely need to automate everything at once. You do need every stage built to join the same system.

  1. Map the line as it runs today

    Rates, stoppages, manual stations and the equipment worth keeping. The integration plan starts from where the line actually loses time, not from a machine list.

  2. Automate the hardest job first

    Usually the heaviest, least staffable station — very often palletizing. It is automated so it can later join the line, not as an island.

  3. Extend upstream

    Case packing and other stations are added in sequence, each connected to the controls architecture laid down in the first stage.

  4. Run it as one line

    Line-level start, stop, fault recovery and changeover — the point where separate machines start behaving as a single system.

Integration or one machine

When you need integration — and when you don't

Integrate the line when

Stoppages happen between machines, not inside them
If each machine is reliable on its own but the line still stops, the problem is the seams — which is exactly what integration addresses.
You are adding more than one machine
Buying a case packer and a palletizer as two separate projects usually means integrating them later, at a higher cost.
Operators run the line from several screens
Separate controls for every machine is a sign the line was assembled, not integrated.

Buy one machine when

Only one station needs automating
A single machine at the end of an otherwise manual line does not need a line-integration project. Buy the machine.
The upstream process is still changing
Integrating around a process that is about to change locks in the wrong design. Settle the process first.
FAQ

Integrated automation questions