Based on. Design and implementation of production management system of NET Platform

1 system analysis and overall design

0 Introduction

Under the impetus of enterprise informatization, some scientific research institutes have established CAPP and PDM systems, but the informatization of production and processing management is still a blank, which leads to many problems in production and processing, such as process data and production data can not be shared, production scheduling mode is backward, Quality information feedback lag and production data feedback is not timely, not conducive to leaders at all levels to grasp the production situation. At the same time, because of the discontinuity of system construction, the basic electronic information exchange can not be carried out between each system, which forms the "Information island" of application system.

The research institute is a typical development and mixed model of many varieties of small batch production, which is different from the batch mode of other large industrial enterprises. This paper analyzes and summarizes the production characteristics and requirements of the enterprises in the research institutes, and combines the management and information technology to design the production management system based on the Scientific Research Institute.

1 system analysis and overall design

The production management system runs through the whole life cycle of the production process, is completely based on B/s architecture design and implementation, the system development and maintenance only on the server side, basically do the client's 0 management, 0 maintenance. The system uses EAI data integration method, integrates with Capp and PDM system, so that it forms two organic whole, so that users don't feel the existence of multiple systems.

1.1 System Function Overview

The overall functions of the system include: production planning management, shop scheduling management, processing flow management and the management of the 4-pack warehouse to manage most of the business functions and interface functions with each external system. The system's functional block diagram is shown in Figure 1.

Figure 1 System features

System to achieve the level of production planning tasks issued to the factory shop scheduling and dispatch, and then to the workshop process dispatching, inspection and other processing flow, and finally to the set out of warehousing, product transfer and other products in the production process of the task life cycle management. Integrated interface functions with other systems include: interface with PDM, deliver design BOM to production and process, interface with document System, track drawing release and recycle, interface with material system, solve data integration and information sharing problem with material storehouse. and CAPP interface to obtain the production management flow of basic data a process data. At the same time, combined with the work center bar code  control, on-site real-time problem feedback interaction, solve the bottleneck problem in the production process constraints, improve production delivery speed.

1.2 System EAI Scheme design

The system EAI design adopts the enterprise application integration technology architecture based on Web service, and the service logic is encapsulated in the form of Web services between the presentation layer of the internal application of the PMS system and the business logic layer, and the presentation layer simply calls the corresponding interface class method library to realize the call and feedback of the business data. In order to achieve the system's established functions. For the external interface of the PMS system, because the document system is a new system, the Web service interface has been provided as needed, so the interaction between PMS and its business logic can be realized only by reference in the PMS system. But like PDM system, CAPP system and material system, all belong to the old legacy system, for these systems, we need to analyze the business model and database model of these systems, construct the corresponding Web service interface and publish the corresponding data information of these systems.

1.3 System Architecture Design

The production management system adopts multilayer architecture design. Multilayer structure has the advantages of reusability, extensibility and low coupling. Each layer can be isolated and reused, and the call between layer and layer reduces the coupling, realizes the system's low coupling, cohesion well-structured classes, facilitates two times development, realizes the software to reuse in the architecture level. The system architecture is shown in Figure 2.

Figure 2 System architecture

The presentation layer provides an interactive interface for applications. Through the action of each role, invoke the business logic of the Web Service layer encapsulation, obtain the result of the business operation, display through the browser interface.

The Web service layer encapsulates the business logic as a Web service, provided to the presentation layer invocation, and is responsible for interacting with the presentation layer operation.

The business logic layer is the core layer of the system, which includes 2 parts of system interface and business function. System interface is integrated with the PMS interface, such as CAPP interface and PDM interface, business functions mainly include user management and authority management, such as general functions and program release, task reception, workshop flow and the management of the same set of business functions. The common component is mainly the encapsulation of some common functions of components, can be used as a reusable component of future systems. In addition, it includes a configuration management layer to manage the system's underlying data, parameters, and log configuration information.

The data access layer provides a uniform data access service to the application, eliminates the direct access to the database and realizes the interaction with the database. The data access layer provides Oracle with customized data access components that optimize access to Oracle databases. Data Access Layer Pass

The use of connection pooling and caching to improve data access speed and efficiency, reduce system overhead, improve the efficiency of the entire Web application system. The data storage layer includes databases and storage files that provide persistent support for business data, process data, and configuration data. In addition, the use of XML and formatted text for temporary storage of data and business interaction, such as the conversion between different BOM.