Traffic

Mobile robots on the floor

The problem Robots idle waiting for a free area, and nobody sees the whole fleet.

intellifix · Traffic Live plant
Data it needs
Fleet managers and line signals
Areas of the operation
Warehouse, palletizing and shipping
Integrates with
OEE · CMMS
How it starts
14-day free trial
What it does

Every robot working with the lines, on one map.

Robots from any vendor working together with the lines: traffic areas reserved and released, pickup triggered when the load is ready.

Fleet managers and line signals
  • Live fleet on the plant drawing
  • Traffic areas reserved and released
  • Pickup triggered when the load is ready
Module screens

The interface, screen by screen.

A capture from the running application, with demonstration data.

intellifix · Traffic Live plant
Live plant
How it works

From the data that comes in to the decision that goes out.

  1. 1

    The plant is drawn

    The plant drawing is calibrated in millimetres, with the zones, the traffic areas and the conveyors marked on it.

  2. 2

    Each fleet joins as it is

    Each vendor's fleet manager stays in command. Its positions and states are translated into one map and one set of statuses.

  3. 3

    Areas are reserved and released

    Before a robot enters a shared area, the area is reserved for it, and released when it leaves. An area that stays stuck raises an alert.

  4. 4

    The line calls the pickup

    When a conveyor signals that the load is ready, the pickup is triggered. An alarm on the line can pause the fleets that serve it.

Requirements

What it takes to go live.

Data it needs

Fleet managers and line signals

This is the hard requirement. Without it, the capability has nothing to read.

What the plant needs

  • Access to each fleet's manager, through a data source.
  • The plant drawing, to be calibrated in millimetres.
  • Signals from the conveyors, such as a pallet ready for pickup.
  • The plant-side runner, which talks to the fleets from inside the plant network.
Where it acts

Where it acts in the plant.

Results delivered

What becomes possible.

  • The whole fleet on one screen, whatever the vendor of each robot.
  • A robot waiting for an area becomes visible, with how long it has been waiting.
  • The pickup happens when the load is ready, not when somebody remembers to call it.
  • Logistics loss per line shows up as a number, not as a complaint.
Examples of use

On the floor, it looks like this.

A pallet waiting at the end of the line

The conveyor signals that the pallet is ready and the pickup is triggered, with nobody on the radio.

Two fleets, one dock

AMRs and autonomous forklifts share the same dock: the area is reserved for one and released for the other.

An alarm on the line

An alarm rule pauses the fleets that serve the line, and the plant map shows which robots stopped.

Benefits by role

What each side of the operation gains.

Operation

The shift sees where each robot is, what it is doing and which area it is holding, on the plant drawing.

Quality and process

Waits and stuck areas are recorded, so a recurring bottleneck has a history and not just a feeling.

Management

Logistics loss per line and the fleet's time by status become numbers you can follow shift by shift.

Integrations

It does not work alone.

Every capability reads from and feeds the others. What this one exchanges inside the operation:

OEE

Efficiency and losses

The time a line stood still waiting for a pallet pickup becomes logistics loss on that line.

Open capability
CMMS

Maintenance

Each robot links to its maintenance asset: plans, orders and battery changes come from there, and a robot under maintenance stays out of operation.

Open capability
Traffic

Want to see this on your own data?

Bring your plant drawing and one fleet. In the demo we calibrate the map and show the robots live.