Currently, Manufacturing related documents are all over the place, Work Order, Job Card, Operations, BOM, Consumption. There is no overview of the production lifecycle at one central place where users can track the whole process and manage it as well.
Elexess has received requirements from two of our clients for such a system. I am sure there might be other manufacturing companies who would love to have something like this.
We gave it some thought and came up with the idea of having a Manufacturing Execution System(MES) in ERPNext. An MES will help achieve that goal by tracking and gathering data about the complete production lifecycle.
We have put together a mockup of what it should look like. The idea is that the user will scan the Work Order and all the information about it will be displayed. And the user will also be able to perform some actions on it like making Consumption, starting stopping the Operation, creating a Job Card.
We have not started on it yet but it is in our pipeline. This will be vue.js page with all these components on it. This off-course requires more discussion and design improvements.
We wanted to have attention from the community and Frappe Team on it. We need to know if this is something that should be developed within the ERPNext, will the core team be interested in something like this, or should we develop it as a separate app. Since it is a huge development, we can use inputs from the core team if they are interested.
We are not asking the core team to develop it, we never do. We always develop and contribute it back. But we do need design discussions with the core team so that we are on the same page, that is how we always work with them.
Class hierarchy can be a source of several pain points. For example, React Hooks solves many pain points of React Classes.
Class hierarchy makes it difficult to manage State because class hierarchy can become deeply nested. It can also introduce unintentional bugs because of unforeseen / unwanted side effects in life cycle methods.
React class is giving way to React Hooks because of this.
Vuejs does not have these pain points precisely by abandoning class methodology and adapting the lego like approach of components.
Frappe is ideal for Vuejs. I sincerely hope more examples like this Manufacturing MES effort can be done in Vuejs. The advantage is:
Code reuse is achieved because pre-built components from other developers in other projects can be reused.
Loosely coupled methodology is easier to debug because you don’t have to dig through the deep hole of class hierarcy.
We integrated Frepple planning engine in the past version for a customer of ours. This is a good opportunity for us to discuss and come up with a great module to be given back to the community. Let us plan on an online meetup with a given agenda and a fixed time?