# SparkMES vs Sepasoft - Production Model Revision Handling

**URL:** <https://forum.inductiveautomation.com/t/sparkmes-vs-sepasoft-production-model-revision-handling/115996>\
**Category:** Ignition\
**Created:** [June 16, 2026, 6:34am UTC](https://forum.inductiveautomation.com/t/sparkmes-vs-sepasoft-production-model-revision-handling/115996 "2026-06-16T06:34:28Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![christopher\_wray](https://avatars.discourse-cdn.com/v4/letter/c/54ee81/32.png) [@christopher\_wray](https://forum.inductiveautomation.com/u/christopher_wray)\
**Post date:** [June 16, 2026, 6:34am UTC](https://forum.inductiveautomation.com/t/sparkmes-vs-sepasoft-production-model-revision-handling/115996/1 "2026-06-16T06:34:28Z")

</div>

Hi all,

I have experience delivering with SparkMES from Flexware Innovations and am evaluating MES module options for a new Ignition 8.3 implementation in a high tech electronics manufacturing environment.

One limitation I noticed with SparkMES is around production model revisions. When you create a new revision of a production model, existing work orders remain on the old revision and only new work orders ingest to the updated revision. This creates a split dataset which can complicate reporting and traceability queries across the revision boundary.

My question is - does Sepasoft handle production model revisions differently? Specifically:

- Can revision updates be applied to existing work orders?
- How does Sepasoft handle reporting and traceability across multiple revisions of the same production model?
- Are there any other MES modules worth considering for track and trace in a precision manufacturing environment?

Any experience from people who have used both platforms would be greatly appreciated.

Thanks

---

_[View the full topic](https://forum.inductiveautomation.com/t/sparkmes-vs-sepasoft-production-model-revision-handling/115996)._