Replies: 3 comments
|
This is hard questioHi @buzzy84, good question. Honestly, the software is already at a tested, working state - the core MES runs end-to-end (production structure, work orders, planner, operator flows, batches, issues/andon, RBAC, reporting, REST + ERP API, desktop and Android builds), it's covered by ~2,000 automated backend tests plus an E2E suite, and it's live on our public demo. From a code and feature standpoint it's in good shape. So the gap to 1.0.0 is not really "more features" - it's real-world validation. Before we put the "stable/production-grade" label on it, we want more companies actually running it in daily production and telling us it's solid enough for everyday work: that the flows fit how they really operate, that it holds up under real load, and that upgrades are painless in practice. That kind of confirmation only comes from real plants using it day to day, not from our own testing or the demo. In other words, 1.0.0 is usage- and feedback-driven, not date-driven. We keep shipping usable minor releases (0.18, 0.19, …) that are safe to deploy today - and every plant that adopts one and reports back moves us directly toward calling it 1.0. If you're considering it for a real plant, that's exactly the kind of validation we're looking for - run it, tell us what works and what doesn't, and you'd be helping define what "1.0" means. Happy to support you through a pilot.n because, every time |
|
Hi @jakub-przepiora sorry for the late feedback, I would be more than happy to try OpenMES out in order to support the development and bugfixing phase. But I have to careful as full deplyment might be taking time, also we have some challanges as we have an ETO production. I'll try to figure out how to start the testing without big impact and come back to you |
|
@buzzy84 if you will have any problems let me know on discord https://discord.gg/U9jM6CCKy or email jakub.przepiora@nice-code.com We will help you. We would appreciate a case study. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello @jakub-przepiora what's the actual implementation plan to reach a stable v.1.0.0 ?
Thank you in advance!
All reactions