Iddan PFT
Process flow tracking
Track every job through every stage. Find your constraint. Fix it first.
Iddan reads the flowchart you already have, measures every stage however it is triggered, and tells you what to change — in a factory, a workshop, a lab or an approvals desk.
Already on a team using Iddan? Ask your admin for access.
Flowchart in. Measurements in. Constraint out.
Iddan does not ask you to describe your process from a blank form. It starts from the flowchart you already have, then watches the work move through it.
Start from your flowchart
Import the diagram you already have — draw.io or Visio — and Iddan drafts your stages from it. You confirm, rename, re-order. Or set them up by hand; both work.
Measure every stage, however it’s triggered
A scan at a station, a button on a bench, a signal from a machine, a stage change inside your software — each one is a timestamp. A stage you don’t control is entered honestly, not faked.
Watch the work flow
Every job, every stage, as a timeline: where it worked, where it waited. Standard and customised jobs are measured apart, so a custom build never hides a slow stage.
Get told what to change
One constraint, in plain English, and a proposed change to your flowchart — written back in the format you gave it to us. You decide; Iddan keeps measuring.
See where the time goes — and where it stops.
Jobs flow left to right through your stages. The width is how many. A flow that stops is work waiting at that stage, with how long it has waited. Rework leaves the line and comes back. The stage with the longest queue is the constraint — and it is marked.
One constraint, not a dashboard
Every Kinara product finds the single thing limiting the business, quantifies it, and says what to do first. Here, that is the stage with the longest queue.
Continuous, not a one-off study
The picture redraws as the work moves. Fix the constraint and the next one shows itself — that is how the flow keeps getting faster.
Filter to what matters
Standard or customised, one factory or all, this week or this quarter. Same picture, narrowed down; tables one tap away.
The name, and the three times.
Every Kinara product’s mark carries its own story. Iddan’s is told in three bands that each stop at their own time.
Every stage has its own set time
Iddan is Aramaic for an appointed time — a set season. Each band is a stage of the work, running from its start to the moment its time is up.
Time layered on time
The stages hand over in order, each starting a little after the last. That is why each band’s gap sits a turn further round: appointed time upon appointed time.
The one that stops last sets the pace
Whichever stage runs longest sets the pace for everything around it. Find it, change it, and the whole flow moves. That is the entire product.
Built for how work actually flows.
A factory floor, a workshop, a lab, an approvals desk — any work that moves through stages. Kinara Analytics is built into every paid Kinara and Qlaim product; in Iddan it is the part that names the constraint.
One constraint, not a dashboard
Not twelve competing metrics. The single stage limiting the flow, how much it costs you, and what to do first.
Standard and custom work, measured apart
A customised job is allowed to take longer. Iddan keeps the two baselines separate, so a slow stage can’t hide behind a complicated order.
Machines and people, judged differently
A laser cutter runs the same every time; a finishing bench doesn’t. Each stage is measured against its own kind of variance, not one blended average.
Stages you re-sequence yourself
Moved a step to the other factory? Change it in Iddan the same afternoon. The flow is yours to edit, and the history stays intact.
Any trigger you already have
QR tags and scan stations, a button on the bench, a machine signal, or a stage change in your other software — a Nahshon pipeline, for one.
A stage you don’t control
Powder-coating at a supplier across the road has no scanner of yours. It is still in the flow, still takes time, and is entered honestly — never faked, never ignored.
Your flow, measured. Your constraint, named.
Import or build your stages, print the tags, and watch the picture fill in. Then let Iddan tell you what to change.
One scan when it’s done. That’s the whole job.
Your station, on the phone or scanner you already have. Finish the stage, scan the tag, carry on. Nothing to fill in.
Ready to see where the time goes?
Register your company, bring your flowchart, and watch the constraint show itself from the first week of scans.