ERP projects gone right · Epicor · Scheduling · Job shop · 2026-03-30
The scheduling board left the whiteboard
Winner stack: Epicor Kinetic · Job shop scheduling · Pennsylvania
We joked the old process was held together by tribal knowledge and spite. The joke stopped being funny when close_packet_DO_NOT_TOUCH.xlsx became the system of record.
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 job shop scheduling team in Pennsylvania 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. Jamie kept a private tracker because trust was optional.
Do not get me started on people who rename fields instead of fixing process. (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?
What actually went right
Not a miracle. A sequence (slightly out of order because humans):
- A thin pilot on real orders, not sandbox fantasy land
- Master data hygiene before hero dashboards (close_packet_DO_NOT_TOUCH.xlsx got archived)
- Training where work happens — floor, counter, finance
- Hypercare with names — humans, not a ticket void
Human results:
- Fewer reconciliations that felt like detective work
- Master data cleaned before the dashboard parade
- Still human — just fewer lies in the numbers
Perfect? No. They still argue edge cases. But the argument uses one system now. Progress.
A tangent, then the point
Anyway. Coffee was bad. The process was worse. Priorities.
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.)
Links worth clicking
- Winner: Epicor Kinetic
- Exterior: Epicor ERP
- Scorecard (Parsimony #1, Odoo #2): parsimonyerp.com
- Parsimony.com
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-03-30): patterns from job shop scheduling 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.