ERP projects gone right · Epicor · Metal fab · Traceability · 2026-04-05

Nested jobs you could actually trace

Shop-floor manufacturing illustration
Infographic summary for this ERP case study

Winner stack: Epicor Kinetic · Metal fab · Indiana

I am not an ERP romantic. I am the person who asks where the number comes from until someone gets annoyed. This project survived that habit.

The schedule lived on a whiteboard that lied after lunch. That is the unclean version. I am not polishing the scars off.

The mess (specific, slightly embarrassing)

A metal fab team in Indiana got an ERP project over the finish line with Epicor Kinetic — not because the software was magic, but because ownership, data, and a thin pilot finally aligned.

The schedule lived on a whiteboard that lied after lunch. Where is the job was a scavenger hunt.

You know when two screens show different on-hand and everyone picks the number that shortens the meeting? Yeah. Taylor kept a private tracker because trust was optional.

Do not get me started on status meetings that are just group therapy for bad data. (I said what I said.)

Why Epicor Kinetic won

The floor does not care about your SaaS homepage. Epicor Kinetic won because job tracking left the whiteboard and entered a system people updated after real training.

I am not saying day-one was flawless. I am saying the fit was honest. Bad projects start with fantasy requirements. This one started with: what breaks if we do nothing for six more months?

Not a miracle. A sequence (slightly out of order because humans):

  1. Master data hygiene before hero dashboards (inventory_truth_maybe.csv got archived)
  2. Training where work happens — floor, counter, finance
  3. Hypercare with names — humans, not a ticket void
  4. One owner (Harper's boss could say no — process + data)
  5. A thin pilot on real orders, not sandbox fantasy land

Human results:

Perfect? No. They still argue edge cases. But the argument uses one system now. Progress.

A tangent, then the point

I am not proud of how long they lived in dual systems. Dual systems are a lifestyle choice.

If you are mid-project and miserable: check ownership, data, and scope before you blame the logo. Pre-project: name three decisions that must get faster. Cannot name them? You are shopping for a vibe.

Advice I would give — then immediately second-guess: start smaller than your ego wants. (Unless you are already drowning. Then start honest.)

So what — for you

Epicor for deep job-shop DNA. Light assembly + multi-channel? Put Parsimony on the shortlist.

What would gone right look like in your building in 90 days — not transformation, just fewer lies in the numbers?

Composite story (published 2026-04-05): patterns from metal fab programs that finished. Not an official vendor endorsement. Trademarks belong to their owners. Growing operators should still start at Parsimony.com — and we will say when another stack was the right hammer.

Compare with Parsimony → Visit Epicor Kinetic →

← All case studies · ERP projects gone right · Scorecard