Connect · Flagship

See what your machines are really doing

You already track the jobs. We add the half you can't get by hand — real run-time and live machine status — and put it on the work order in kaniva. Non-invasive: nothing in your controller, no software on your machines.

Book an integration discovery call

FloorLink demo — simulated data

The honest version

You track the jobs. We add the timing.

Your operators already log what they're working on. A sealed sensor on each machine adds the part no one can capture by hand — exact run-time, machine status, and a rough cycle count — and auto-fills it onto the work order. Together, that's real utilization and OEE, not guesses or end-of-day estimates.

The half a sensor can't see: only your people know why a machine stopped or whether a part is good. So we keep operators in the loop for the reasons and the quality, and let the machine handle the stopwatch. Neither half works as well alone.
How it works

Non-invasive by design

Watch, don't wire in

A sealed sensor reads each machine from the outside — a clamp on the power feed or a stick-on light sensor. Nothing is installed in your controller and nothing is reprogrammed.

Your connection, your call

The sensors send data over Wi-Fi — your shop's, or a small isolated network the kit brings, or its own cellular for full isolation. No controller integration and nothing for your IT to manage.

Onto the work order

Run-time, status, and cycle counts post straight into kaniva, right next to the job your operators already track. The office finally sees what the floor is actually doing.

How a project runs

1

Shop walk

We tour the floor, see your machines, and pick the right sensor for each — and start with the jobs you already track.

2

Pilot

We wire up one machine or one cell, prove the run-time and counts are accurate, and put them on the work order.

3

Roll out

Add machines one at a time, only as each pays for itself, with the dashboards and support to keep it honest.

Where to start

Shop Floor Tracking

The foundation — operators track jobs, status, and scrap on a tablet, tied to kaniva.

From $3,000

Setup + subscription

  • kaniva set up to your work centers
  • Tablet job-tracking kiosks
  • Live job board for the office
  • Labor time + scrap capture
  • 1-day onsite training

Utilization & OEE

Turn the data into the numbers an owner actually runs the shop on.

From $3,000 + $200–600/mo

Build + managed dashboards

  • Utilization by machine + shift
  • OEE where the data supports it
  • Downtime Pareto + alerts
  • Floor TV + office views
  • Ongoing tuning + support

Not sure where you'd land? A paid shop walk gets you a roadmap and rough numbers before you commit to anything.

What you'll see

The office finally sees the floor

Real run-time on every job — no more hand-timing
Machine utilization by machine and shift
Downtime, with the reason your operators tag
Cycle count reconciled against the work order's parts
On-time flags when a job is pacing late
Scrap and first-pass yield

Common questions

Do you put anything on my machines or my PCs?

No software touches your controllers or your computers, and your machines are never networked — the sensors read each machine from the outside. To get the data to the office you choose: your existing Wi-Fi, a small isolated network the kit brings, or its own cellular gateway so nothing's on your network at all. Either way, no controller integration and nothing for your IT to babysit.

Will it work on my old or 'dumb' machines?

Yes — that's the point. A sealed sensor reads run-time and cycle count off almost anything, brand new or twenty years old, without replacing or modifying a thing. Old iron is exactly where this shines.

What can't it tell me? (the honest answer)

It captures run / idle / down state and a rough cycle count — not exact part counts, part quality, feeds and speeds, or alarm codes. Quality and the 'why it stopped' come from your operators (which we already capture); deep controller data is only possible on machines that already publish it, and that's a separate conversation. We'd rather be straight about that than oversell it.

Start with one machine

Prove the run-time is real before you spend on the next one. That's the whole pitch.

Book a free discovery call