Insights

Know where the line is slow. And what built every unit.

Predetermined time studies sit beside the actual cycle times your floor captures, so bottlenecks and capacity stop being guesswork. Every serial you ship carries its full kit-level lineage. Every component, every sub-assembly, every operator, every approval.

Bottleneck + capacity insight

Target vs. actual. Every station

The cycle-time chart pairs target (from the engineering library) with actual (captured at build time) for every station on a line. Green where the floor is hitting takt, amber where it's drifting, red where the station is the line's bottleneck. Right-size capacity with the same data your operators feel, not estimates.

  • Target vs. actual cycle time per workstation, last 7/30/90 days
  • Bottleneck visible at a glance. Colour-coded against takt
  • Actuals captured at build time. No manual stopwatch
  • Roll-up by line / by plant / org-wide
Downtime by reason
Last 30 days · Brake corner line
48.5 h
total lost
  • Equipment · Compressor
    18.4 h
    100%
  • Material · Kit not staged
    12.1 h
    66%
  • Equipment · Torque tool
    8.7 h
    47%
  • Labor · Operator change
    5.2 h
    28%
  • Planned · Maintenance
    4.1 h
    22%
Throughput, defect, downtime

Three more charts you stop drawing in Excel

Throughput by day with a target overlay. Defect pareto by reason and sub-reason. So the brake-caliper line's "over tolerance. Bore" either drops or shows you exactly where to put the engineering hour. Downtime pareto by reason. Equipment, material, planned. So you fix root cause instead of arguing about it.

  • Throughput chart with daily build counts + 7-day average
  • Defect rate + pareto by category → sub-category
  • Downtime pareto by reason with time + frequency
  • Date-range chips: 7d / 30d / 90d, per line filter
  • Sparky chart narration — one-line plain-language read on what each chart is actually showing, with the obvious next action
Kit-level traceability

Full lineage for every serial

Pull any serial and see the tree: vehicle BC-260517-0023 ← caliper sub-assembly CA-26051-0019 ← rotor R-260517-091, harness H-260517-008, fasteners by lot. Every operator, every timestamp, every approval. The recall conversation goes from "we think we know" to "here are the 47 units affected, here is the operator at the join station, here is the WI revision that was published that day".

  • Full upstream lineage captured at build commit. Never reconstructed
  • Parallel sub-assemblies that merge into one parent serial
  • Scan-required parent serials recorded with operator + timestamp
  • Traceability without extra paperwork. Falls out of the build flow
Get started

Ready to run your line on Ignite Lean?

Free during early access — 1 manager seat included, unlimited operators.

Get early access