SparkMES vs Sepasoft - Production Model Revision Handling

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