U-type theory based on Small Enterprise Informatization (5)

BOM construction is one of the key aspects of system design
In this U-type theory, there are no modules such as the main production plan and Capability Requirement Plan in MRPII, the reason for this is that the companies we met did not think about Bom because the products are not made and assembled. However, the fact is being used, for example, the carton factory uses Cart to produce carton, the number of Carton Boxes ordered by the customer is rarely the same, while the number of carton is the main material. It can be calculated according to the formula, and the remaining nails, glue, and ink can be ignored, therefore, it is absolutely impossible for them to add a new BOM record every time they add a new kind of carton, instead, the corresponding Program is designed to automatically replace the BOM expansion. After I made a few systems, I felt that there was a correct sentence: BOM building is one of the key points of system design. This U-type model also expresses this idea. For small enterprises or industries of different nature, MRPII cannot be used for MRPII. I would rather replace MRPII with the term "Management Information System.

However, it is undeniable that this is a relatively superficial theoretical model, which first does not reflect the use of human resources. In this module, it is only an independent personnel management module, the depth is also a comparison of working hours in the production plan. Secondly, it does not take time as the axis, and does not intuitively reflect the relationship between time. For the planned date and completion date, only the query interface provided by the Plan feedback is used, while other time relationships are made based on the time x axis, similar to the Gantt Chart content, this is far from the U type.
when I discussed the theoretical model in the training of enterprise information managers, I was given advice from teachers and students. Some teachers pointed out that the extension can be easily implemented, for example, sales in Cost awareness can be expanded to control the customer's credit line based on historical records. My current practice is to directly enter the credit line in the customer file, the prompt is displayed when the order is entered for review. Therefore, it still has the opportunity to mine and enhance its confidence. Another teacher proposed a very classic formula: A * B-C = D, here a requires production, B is the ratio in Bom, C is the raw material inventory (finished product inventory ), D is the purchase volume (production volume). In this model, the formula is shown as follows:
some people pointed out that the left side of the U type is actually information flow, and the right side is logistics, the supplement in the picture on the right is capital flow, although this is my first-class three-stream (enterprise management includes Logistics, capital flow, and human flow, and information flow is the carrier of the above three) there is a conflict of ideas, but it brings my U-type model closer to the first-class three-stream idea. It may be integrated at some time in the future.
In addition, I also see a more similar (for example) on the CIO website. Its idea is similar to mine. However, the relationship between customers, sales, production, procurement, and manufacturers is shown in
.
I believe that, with the help of everyone and the efforts of others, the U-type theory will become more and more perfect and can truly contribute to the informatization of small enterprises.
full text