Keeping MES simple
We want to keep MES simple
We like to keep things simple and so is our MES model. That is, our model has only four basic entities - tell building blocks- from which a complete operation model can be made. Based on the four basic abstract entities the customer can build his own model with its own entities, properties, methods, in his own words and rules .
If a cleaning operation is referred to as "celkuising" in the world of our customer, with the properties like "First trip made", "Second trip made", "Third trip made" with the method "Run tour" and that the rule is that after the first trip the third trip follows, ... who are we to contradict them?
Other examples include company-specific KPIs. The customer decides.
Our licensing model is simple. Licenses are based on the number of servers in the cloud and the number of clients used. We have no staffel to the number of data points and we have no modules.