3 ways to divide your business for better use of APS

When you start thinking about implementing an APS solution, one of the first questions that arises is: "Should we divide the company into different models? And how do we do that?" Well, first, we should discuss what a model is? We call a model an independent unit of the APS system. Just as in mathematical problems, we model a real problem and transform it into a theoretical one. However, instead of writing a mathematical expression, we do so using the APS system. Therefore, in complex production chains within the mes company, the division of APS models can directly influence the quality and adherence of the solution. Therefore, it is always important to discuss the positive and negative impacts of each architecture we will adopt. The major tradeoff in this part of the project is that the more we separate the models, the more the holistic view of the factory is compromised. However, the more we group the models, the more complex the solution becomes. To illustrate, we separate three types of modeling divisions: 1 - Physical Division. This is perhaps the most natural of all and often occurs without discussion. Imagine the example of a company with headquarters in Porto Alegre and São Paulo. Originally, these two locations will probably each have a programmer, with their own programming rules, specific parameters, and other basic differences. To give the two plants proper independence, it may be worthwhile to design an independent model for each. 2 - Division by Parallel Process. Now, let's imagine that this mes company produces two types of products (pens and pencils). It may be worthwhile to separate each type of product into a model, mes if they are produced at mes headquarters. However, be very careful when performing this step; we must satisfy a basic premise of sequencing: the mes resource can only be sequenced by one model. In other words, the machines that produce the pen components will not produce the pencil components, thus ensuring that the flow of each type of product does not mix with the flow of the other. 3 - Division by Serial Process Another common example is to have a model by production stage. For example, if our pen factory were separated into Assembly and Packaging sectors. This division may make a lot of sense to provide process independence, but it also requires a procedural division between these two sectors, for example, a stock of assembled pens for the packaging sector. In these cases, grouping these sectors can be a great benefit to have a view of the production order flow and the impact of a schedule change on the other process. So, as we can see, it is possible to design the solution in different ways for an APS implementation project, demonstrating how flexible and adaptable this solution is to various production chains combined with market experience. Now tell us, what would be the best architecture for yours? [noptin-form id=2822]