Use the. NET platform to build an enterprise application system field (I)

This articleArticleWe will introduce a simple solution for building an Enterprise Application Reuse System. This solution is suitable for enterprises as Party A to integrate existing systems and integrate internal software developed by enterprises.

At present, large and medium-sized enterprises have many internal information systems, basically multi-system collaborative work, such as ERP, HR, protal, fa, etc. Some systems belong to the enterprise's core systems and some belong to daily office systems, the bidding has the following characteristics: Business Department + It Project Team + Party A company. These three departments collect and analyze internal requirements of the company and standardize some systems, it may even change the old production and operation processes of some enterprises, but it will almost ignore a problem at the same time and hardly realize the flexibility and agility of the system. This will inevitably form an information island phenomenon, this phenomenon will cause a large amount of information to stagnate and cause losses to enterprises. The amount of money spent by enterprises to solve this problem is also high.

The so-called information islands refers to the isolation between departments and departments due to various reasons in a unit, and various information (such as financial information and various plan information) you cannot or cannot smoothly flow between departments. In this way, information islands will be formed. It is a manifestation of hard, soft, and network-light data.

For example, for a production enterprise, the sales department should have its own sales plan, and the workshop should formulate its own production plan based on the sales plan and the inventory of the warehouse, the procurement department should develop its own procurement plan based on the workshop production plan and inventory of warehouse raw materials. In many enterprises, this process is not smooth or even unreasonable. The sales department does not consider the production capacity of the workshop when formulating the sales plan, and the production capacity of the workshop does not consider the digestion capacity of the market, the procurement department does not advocate blind Procurement Based on the workshop plan. In the end, the inventory of the warehouse is too large or serious cargo disconnection occurs. In this case, all departments in such an enterprise are isolated information islands. To avoid such islands, we need to introduce the concept of "field, the field solves the problem based on abstraction.

 

 

How is an information islands formed?

1. traditional systems have bottlenecks. The bottleneck mentioned here is not the bottleneck of the technology itself. Some old technologies also have high availability, and their ideas are irrelevant to specific technologies, therefore, the bottleneck here refers to the bottleneck caused by people. As described in the project composition method, no organization will think that these systems will cause information islands in the future, integration of these islands will cost 10 times or even dozens of times more than the cost of a project. In addition, the integration work is highly risky and the benefits are not obvious. It investment-income ratio is hard to calculate, it can be said that it is precisely because we are too familiar with the project and did not use software engineering ideas flexibly and extensively in the overall IT construction that leads to information islands.

 

I amAicken)Welcome to my next article