KR20240039783A - Smart factory system - Google Patents

Abstract

The present invention relates to a smart factory system in which all facilities and devices are connected through wireless communication, allowing the entire process to be monitored and analyzed in real time. The smart factory system according to the present invention includes an MES server, wherein the MES server includes a standard information management module that manages information that becomes the standard of the smart factory system, and a sales management module that registers and manages information related to product sales. module, a quality control module that registers and manages documents related to product quality, an equipment management module that registers and manages information related to the import/exit, repair, and calibration of equipment, and a test management module that registers and manages information related to the testing process. module, a sample management module that registers and manages information related to the received and registered samples, a system management module that registers and manages information related to the operation of the smart factory system, a monitoring module that registers and manages information within the testing laboratory, and It includes a production management module that registers and manages product-related information, and a materials management module that registers and manages information on ordering and receiving materials.

Description

Smart Factory System{SMART FACTORY SYSTEM}

The present invention relates to a smart factory system in which all facilities and devices are connected through wireless communication, allowing the entire process to be monitored and analyzed in real time.

For manufacturers, production is the core of their business. Therefore, manufacturers seek to optimize production sites and reduce production site costs. Therefore, a factory that makes decisions quickly, a strategic factory, a factory that responds quickly to the surrounding environment, a factory with minimal operating costs, a factory that is easy to control and operate, and a factory that is easy to build systems are what all manufacturing companies pursue. The system that emerged to support this is the Manufacturing Execution System (MES).

The manufacturing execution system is a concept and implementation tool for manufacturing factory management. This was first introduced in the early 1990s by AMR (Advanced Manufacturing Research), a consulting company located in Boston, Massachusetts, USA. It divided the manufacturing system hierarchy into three layers: planning/execution/control, and defined the execution function as MES. did.

According to MESA (Manufacturing Execution System Association), an international MES association, MES provides relevant information from ordering to product production so that it can be utilized most effectively, and by using accurate field data, field activities can be monitored whenever data is generated. It is a production execution management system that manages, initiates, responds, and reports.

MES supports the optimization of all production activities from the product ordering stage to the completion stage. To achieve this, MES uses real-time, accurate data to guide, initiate, respond to, and report on all work activities within the factory. It also increases the efficiency of work and processes within the factory by focusing on quick response to status changes and reduction of non-value-added work activities.

Quick response to changes in production line conditions, along with a focus on reducing non-value-added activities, ensures effective operation of field operations and processes, and provides important information about the supply chain and the company's overall production activities through two-way communication. . MES is widely used in manufacturing sectors such as automobiles, semiconductors, electronics, food manufacturing, pharmacy, aviation, medical devices, tires, steel, and textile manufacturing.

MES provides information for optimizing production after receiving a product order until the product is completed, reports the latest information occurring at the production site to field workers or managers, and changes production conditions through rapid response. and induces improvement in production processes and functions by reducing valueless elements. Therefore, MES not only improves the efficiency of a company's assets, but also improves accurate delivery, inventory circulation, overall net profit, and fund flow capabilities.

Meanwhile, Smart Factory is an innovative change in the production factory brought about by Industry 4.0, using information and communication technology (ICT) that combines digital automation solutions in the production process such as design, development, manufacturing, distribution, and logistics. It refers to an intelligent production factory that improves productivity, quality, and customer satisfaction by applying . A smart factory can collect process data in real time by installing the Internet of Things (IoT) on equipment and machines within the factory, analyze it, and control it according to the intended purpose. Smart factories have recently emerged as a way to innovate manufacturing industries as light and flexible production systems are required.

Republic of Korea Patent Publication No. 10-2022-0121745 (published on September 1, 2022)

The purpose of the present invention to solve the above-described problems is to provide a smart factory system.

In order to achieve the above-described purpose, the smart factory system according to an embodiment of the present invention includes an MES server, and the MES server includes a standard information management module and product that manages information that is the standard of the smart factory system. Sales management module that registers and manages information related to business, quality control module that registers and manages documents related to product quality, equipment management module that registers and manages information related to the import/exit, repair and calibration of equipment, and testing. A test management module that registers and manages information related to the process, a sample management module that registers and manages information related to the received and registered samples, a system management module that registers and manages information related to the operation of the smart factory system, and a testing laboratory. It includes a monitoring module that registers and manages internal information, a production management module that registers and manages information related to manufactured products, and a material management module that registers and manages information on ordering and receiving materials.

The standard information management module includes the item management department, BOM management department, quotation management department, employee management department, business trip management department, customer management department, transaction history management department, certificate management department, customer management department, business management department, meeting minutes department, material management department, product management department, process management department, and It includes a basic inventory management department, and the sales management module includes a test quotation management department, transaction history status department, consultation schedule calendar department, consultation schedule status department, contract management department, customer management department, performance management department, A/S management department, and after-sales service processing. It includes a status department, customer request deadline management department, product order management department, and product quotation management department, and the quality management module includes the quality document management department, quality document record management department, KOLAS meeting minutes department, training management department, practical management department, security management department, safety management department, It includes a gas cylinder inventory status book, a gas cylinder entry log book, and a gas cylinder export log book, and the equipment management module includes an equipment import/export status unit, an equipment export management unit, an equipment import management unit, an equipment information management unit, an equipment repair management unit, an equipment calibration management ledger, and Includes equipment usage log.

The test management module includes a test application management department, a test progress status department, a test preparation register, a test data management department, a test result management department, a report management department, and a report revision request department, and the sample management module includes a sample warehousing management department and a sample warehousing management department. and a sample inventory status department, and the system management module includes a code management department, a user setting department, a user application management department, a department management department, a rank management department, a corporate information management department, a log management department, a schedule management department, an approval form department, and a barcode management department. .

The monitoring module includes a report issuance status section, a test progress status section, a temperature and humidity status section, a defect rate status section, a test site environment setting section, a first equipment data status section, and a second equipment data status section, and the production management module includes, Schedule Management Department, Progress Status Department, Quality Management Department, Performance Management Department, Purchasing and Inventory Management Department, Outsourcing Production Management Department, Arrival/Delivery Management Department, Product Delivery Status Department, Product Delivery Management Department, Product Arrival/Delivery Status Department, Product Inventory Status Department, Work Planning Department, Work It includes an instruction management department, a work waiting status department, a work log management department, and a work defect management department, and the material management module includes a material order management department, a material warehousing management department, a material shipment management department, a material arrival and departure status department, a material inventory status department, and a material inventory management department. Includes.

The smart factory system further includes an intranet server, wherein the intranet server includes a schedule module for registering and managing monthly, weekly, and daily schedules, a work log module for registering and managing daily tasks and weekly tasks, and setting a payment route. It includes an electronic payment module that manages ongoing and completed payment documents, a notice module that allows the administrator to register notices, and a user management module that sets the user's permission to access the smart factory system.

According to the smart factory system of the present invention, all facilities and devices are connected through wireless communication, which has the effect of monitoring and analyzing the entire process in real time.

Figure 1 is a block diagram showing each configuration of a smart factory system according to the present invention.
Figure 2 is a block diagram showing in detail each configuration of the smart factory system according to the present invention.
Figure 3 is a block diagram showing each configuration of the standard information management module according to the present invention.
Figure 4 is a block diagram showing each configuration of the sales management module according to the present invention.
Figure 5 is a block diagram showing each configuration of the quality control module according to the present invention.
Figure 6 is a block diagram showing each configuration of the equipment management module according to the present invention.
Figure 7 is a block diagram showing each configuration of the test management module according to the present invention.
Figure 8 is a block diagram showing each configuration of the sample management module according to the present invention.
Figure 9 is a block diagram showing each configuration of the system management module according to the present invention.
Figure 10 is a block diagram showing each configuration of the monitoring module according to the present invention.
Figure 11 is a block diagram showing each configuration of the production management module according to the present invention.
Figure 12 is a block diagram showing each configuration of the material management module according to the present invention.
Figure 13 is a block diagram showing each configuration of the schedule module according to the present invention.
Figure 14 is a block diagram showing each configuration of the work log module according to the present invention.
Figure 15 is a block diagram showing each configuration of the electronic payment module according to the present invention.
Figure 16 is a block diagram showing each configuration of the user management module according to the present invention.
Figure 17 is a block diagram showing a smart factory system further including a data management server according to the present invention.
Figure 18 is a diagram showing each module of the data management server according to the present invention.
Figure 19 is a diagram showing each configuration of the data integration management module according to the present invention.
Figure 20 is a diagram showing each configuration of the network drive module according to the present invention.
Figure 21 is a diagram showing each configuration of the backup module according to the present invention.
Figure 22 is a diagram showing each configuration of the backup agent unit according to the present invention.
Figure 23 is a diagram showing an embodiment of a server load diagram according to the present invention.
Figure 24 is a diagram showing another embodiment of a server load diagram according to the present invention.
Figure 25 is a diagram showing another embodiment of a server load diagram according to the present invention.

Hereinafter, some embodiments of the present invention will be described in detail through illustrative drawings. When adding reference signs to components in each drawing, it should be noted that the same components are given the same reference numerals as much as possible even if they are shown in different drawings.

Also, in describing embodiments of the present invention, if detailed descriptions of related known configurations or functions are judged to impede understanding of the embodiments of the present invention, the detailed descriptions will be omitted.

Additionally, when describing the components of an embodiment of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, order, or order of the component is not limited by the term.

In this specification, singular forms also include plural forms unless specifically stated in the phrase. As used in the specification, “comprises” and/or “including” does not exclude the presence or addition of one or more other components in addition to the mentioned components.

Hereinafter, the present invention will be described in more detail with reference to the attached drawings.

FIG. 1 is a block diagram briefly showing each configuration of the smart factory system 1000 according to the present invention, and FIG. 2 is a block diagram showing each configuration of the smart factory system 1000 according to the present invention in detail.

Referring to FIG. 1, the smart factory system 1000 according to the present invention includes an MES server 100 and an intranet server 200.

First, the MES server 100 performs resource allocation and status management, operation/detail scheduling, dispatching production units, document control, data aggregation, and Data collection/acquisition, labor management, quality management, process control, maintenance management, product tracking and genealogy, and execution analysis. In order to provide functions such as (performance analysis) to the user terminal 10, the following detailed configuration is included.

Referring to FIG. 2, the MES server 100 includes a standard information management module 101 that manages information that becomes the standard of the smart factory system 1000, and a sales management module that registers and manages information related to product sales. (111), a quality control module (121) that registers and manages documents related to product quality, an equipment management module (131) that registers and manages information related to the import/exit, repair, and calibration of equipment, and a process related to testing. A test management module 141 that registers and manages information, a sample management module 151 that registers and manages information related to received and registered samples, and a test management module 151 that registers and manages information related to the operation of the smart factory system 1000. A system management module (161), a monitoring module (171) that registers and manages information within the testing laboratory, a production management module (181) that registers and manages information related to manufactured products, and information on ordering and receipt of materials. Includes a material management module (191) to manage.

And the intranet server 200 includes a schedule module 201 that registers and manages monthly, weekly, and daily schedules, a work log module 211 that registers and manages daily tasks and weekly tasks, and a payment route that sets the in-progress and completed tasks. The electronic payment module 221, which manages payment documents, the notice module 231, where the administrator registers notices, and the user, that is, the user terminal 10, are given permission to access the smart factory system 1000. It includes a user management module 241 that does.

Meanwhile, the information input, registered, and managed by the MES server 100 and the intranet server 200 is stored in the data management server 300, which will be described later, and is sent to the user terminal 10 that connects to the data management server 300. That information can be provided.

Hereinafter, each configuration within the MES server 100 will be described in detail with reference to FIGS. 3 to 12.

Figure 3 is a block diagram showing each configuration of the reference information management module 101 according to the present invention.

Referring to FIG. 3, the standard information management module 101 of the MES server 100 includes an item management department, BOM management department, quotation management department, employee management department, business trip management department, business partner management department, transaction history management department, certificate management department, customer management department, and business management department. It includes the management department, meeting minutes department, material management department, product management department, process management department, and basic inventory management department.

The standard information management module 101 inputs, registers, and manages information that becomes the standard of the program. Specifically, the item management department classifies and registers the finished products produced and manages the item classification of materials and products. The BOM management department classifies and registers the materials (required quantity, etc.) used in producing finished products. The quotation management department registers and manages quotations other than test quotations. The employee management department inputs and manages employees’ monthly attendance information. The business trip management department registers and manages business trip information during business trips. The customer management department registers and manages customers for purchases and sales. The transaction history management department registers and manages expenditure details. The certificate management department registers and manages the certificates it holds. The customer management department registers and manages information on customers issuing test reports. The name of the Customer Management Department may be changed to the Test Customer Management Department. The project management department registers and manages support project and project information. The minutes book prepares, registers, and manages general, weekly, and customer meeting minutes. The Materials Management Department registers and manages basic materials required for BOM management. The product management department enters and registers the details of the product being produced. Additionally, the product management department registers and manages products managed or sold by the company. The process management department registers and manages the list of processes involved in production. The basic inventory management department manages inventory when materials and products do not match current inventory.

Figure 4 is a block diagram showing each configuration of the sales management module 111 according to the present invention.

Referring to FIG. 4, the sales management module 111 of the MES server 100 includes a test quotation management department, transaction history status department, consultation schedule calendar department, consultation schedule status department, contract management department, customer management department, performance management department, and A/ It includes S Management Department, A/S Processing Status Department, Customer Request Deadline Management Department, Product Order Management Department, and Product Quotation Management Department.

The test quotation management department registers the quotation registered in the test application for test management. The transaction history status section provides inquiries on tax invoices, deposit registration, and status of quotes registered in the sales management module (111). The consultation schedule calendar section displays the consultation schedule in the form of a calendar. The consultation schedule status section provides registration of consultation content and status. The contract management department registers and manages contracts for various business partners. The customer management department registers and manages information on customers issuing test reports. The customer management department of the sales management module 111 may have the same configuration as the customer management department of the standard information management module 101. The performance management department registers and manages the performance of each person as an attached file. The A/S management department provides A/S reception for products that have been shipped. The A/S processing status department provides status inquiry and repair registration once the A/S application is confirmed. The customer request deadline management department uploads a questionnaire provided to customers when the report is completed. Meanwhile, the name of the Customer Request Closing Management Department may be changed to the Customer Satisfaction Management Department. The Product Order Management Department manages the details and status of product orders. The product quotation management department creates quotations when selling products.

Figure 5 is a block diagram showing each configuration of the quality control module 121 according to the present invention.

Referring to FIG. 5, the quality control module 121 of the MES server 100 includes a quality document management department, a quality document record management department, a KOLAS meeting minutes department, an education management department, a practice management department, a security management department, a safety management department, a gas cylinder inventory status department, Includes gas cylinder import log book and gas cylinder export log book.

The quality control module 121 can register and manage overall KOLAS (Korea Laboratory Accreditation Scheme) documents. Specifically, the Quality Document Management Department registers and manages quality document manuals, procedures, and forms. The Quality Document Records Management Department records and manages the forms registered in the quality documents. The KOLAS meeting minutes record the KOLAS meeting minutes. Meanwhile, KOLAS meeting minutes can also be recorded in the meeting minutes of the standard information management module (101). The KOLAS meeting minutes can also manage documents from external sources. In other words, the KOLAS meeting minutes records and manages external source documents (KOLAS operating instructions and guidelines, test specifications and standards), e-KOLAS documents, and/or external evaluation data. The Education Management Department prepares and manages the annual education and training plan and education results report. The practical management department prepares and manages practitioners' job assignment tables, individual history cards, qualification evaluation sheets, job descriptions, qualification certificates, and practitioner competency monitoring. The security management department provides upload and download of security management policies. Additionally, the security management department provides USB rental and return status. The safety management department records and manages safety training status, eye inspection status, safety management regulations, etc. The gas cylinder inventory status department determines the current inventory status of gas cylinders and provides a warning message if there are more than 15 gas cylinders in stock. The gas cylinder import log allows you to enter and manage the type of gas and detailed information when bringing in a gas cylinder. The gas cylinder export log registers and manages gas cylinder export information.

Figure 6 is a block diagram showing each configuration of the equipment management module 131 according to the present invention.

Referring to FIG. 6, the equipment management module 131 of the MES server 100 includes an equipment import/export status department, an equipment export management department, an equipment import management department, an equipment information management department, an equipment repair management department, an equipment calibration management ledger, and an equipment usage log. Includes.

The equipment management module 131 records and manages equipment import/exit, repair, calibration, etc. Specifically, the equipment import/exit status department records and manages the equipment import/exit status. The equipment import and export status department may be clearly renamed to the equipment import and export ledger. The Equipment Export Management Department records and manages equipment within the laboratory when it is exported to the outside. The Equipment Import Management Department records and manages the import status of exported equipment and externally imported equipment. The equipment information management department records and manages equipment information management, equipment list management, equipment location, equipment calibration status (date), addition of new equipment, etc. The name of the Equipment Information Management Department may be changed to Equipment History Management. The Equipment Repair Management Department registers and manages equipment calibration, inspection, and repair details. At this time, the equipment repair management department can check the equipment history card. The name of the Equipment Repair Management Department may be changed to Equipment Management List. The equipment calibration management ledger records the progress of calibration and provides confirmation of the presence of intermediate inspections. The equipment usage log manages the equipment usage history for each equipment.

Figure 7 is a block diagram showing each configuration of the test management module 141 according to the present invention.

Referring to FIG. 7, the test management module 141 of the MES server 100 includes a test application management department, a test progress status department, a test preparation register, a test data management department, a test results management department, a report management department, and a report revision request department. .

The test management module 141 manages the overall process of the test. Specifically, the Test Application Management Department registers and manages test applications. The test progress status department records and manages the test progress (including test location registration). The name of the test progress status section may be changed to test progress management and status. The test preparation register uploads a checklist before proceeding with the test. The name of the test preparation register may be changed to test preparation check. The Test Data Management (RawData) Department can upload RawData and request approval from the technical manager. The test results management department can prepare and modify test reports and request approval from the technical manager. The report management department provides report report search and screen output. The Transcript Correction Request Department provides corrections and/or reissue of issued transcripts. The name of the Transcript Correction Request Department may be changed to the Transcript Correction/Reissuance Department.

Figure 8 is a block diagram showing each configuration of the sample management module 151 according to the present invention.

Referring to FIG. 8, the sample management module 151 of the MES server 100 includes a sample warehousing management unit, a sample warehousing management unit, and a sample inventory status unit.

The sample management module 151 manages registered samples. Specifically, the Sample Receiving Management Department assigns barcodes to received samples and registers them. The name of the sample receipt management department may be changed to the sample registration management department. The sample entry/exit management department can record and manage the storage, use, and/or status of samples. The name of the Sample Input/Output Management Department may be changed to the Sample History Management Department. The sample inventory status department determines the status (in/out) of samples. The name of the Sample Inventory Status Department may be changed to the Sample Inventory Status Department.

Figure 9 is a block diagram showing each configuration of the system management module 161 according to the present invention.

Referring to FIG. 9, the system management module 161 of the MES server 100 includes a code management department, a user setting department, a user application management department, a department management department, a position management department, a corporate information management department, a log management department, a schedule management department, and an approval form department. and a barcode management unit.

The code management department manages all codes in the select box, including unit and customer classification. The user setting section provides user addition, user-specific menus, and modification of user information. The user application management department approves new ID applications. The department management department provides addition, modification and deletion of departments. The position management department provides the addition, modification and deletion of positions. The Corporate Information Management Department registers and manages the company's basic information. The log management unit provides confirmation of the connection status of the user terminal 10. The schedule management department provides registration of schedule classification and color. The approval form department provides changes to the meeting minutes format. The barcode management department provides barcode information registration.

Figure 10 is a block diagram showing each configuration of the monitoring module 171 according to the present invention.

Referring to FIG. 10, the monitoring module 171 of the MES server 100 includes a report issuance status section, a test progress status section, a temperature and humidity status section, a defect rate status section, a test site environment setting section, a first equipment data status section, and a second equipment data status section. 2 Includes equipment data status section.

The transcript issuance status department provides confirmation of the status of transcripts that have been completed until issuance. The test progress status section provides the progress status of the test registered on the MES server 100 in percentage terms. The Temperature and Humidity Status Department provides registration and confirmation of the temperature and humidity of the testing laboratory. The defect rate status department makes it possible to check the status of defective products among products processed in production management. The test laboratory environment setting department provides functions to register and confirm the details of the test laboratory environment (organizing equipment and materials, recording temperature and humidity standards, safety inspection, etc.). The name of the Laboratory Environment Setting Department may be changed to Laboratory Environment Management. The first equipment data status section provides a logsheet check function for WS2 CVD equipment. The second equipment data status section provides a logsheet check function for MoS2 CVD equipment.

Figure 11 is a block diagram showing each configuration of the production management module 181 according to the present invention.

Referring to FIG. 11, the production management module 181 of the MES server 100 includes a schedule management department, a progress status department, a quality management department, a performance management department, a purchasing and inventory management department, an outsourcing production management department, an inventory/delivery management department, and a product waiting status department. , Product shipment management department, product arrival and departure status department, product inventory status department, work planning department, work order management department, work waiting status department, work log management department, and work defect management department.

The schedule management department allows you to check the progress made in the work plan on the calendar, and also provides functions for registering and modifying the work plan. The progress status section provides registration functions such as production completion request date and production order date, and provides registration and modification functions to determine how much of the current process has progressed among the total process flow. The quality control department provides registration and confirmation of inspection status among manufactured products. The performance management department provides the function to select the quantity and storage location of the produced product and register it as inventory. The Purchasing and Inventory Management Department provides registration of purchased materials and products and provides inventory confirmation. The purchasing and inventory management department can provide the same functions as the basic inventory management department. The outsourced production management department provides a registration function for contents managed by outsourced production rather than in-house production, and allows registration and confirmation of the name of the outsourced production, business partners, etc. The warehouse/delivery management department registers and manages outsourced products. The product shipment waiting status department manages the list to be shipped through the sales management module (111) and the product order management department. The product shipment management department registers and manages orders that have been completed from the waiting status to shipment. The product arrival and departure status section provides a function that allows you to check the status of incoming and shipped products. The product inventory status section provides a function that allows you to check the status of product inventory. The work planning department registers work plans before issuing work orders. When registering a work plan, its contents are reflected in the schedule management calendar. The work order management department registers and manages work orders for products to be produced. The work standby status department registers and manages good/defective products in each production process based on registered work instructions. The work log management department provides functions to view, modify, and delete contents registered in the work queue. The work defect management department registers and manages defects before the registered production work is completed.

Figure 12 is a block diagram showing each configuration of the material management module 191 according to the present invention.

Referring to FIG. 12, the material management module 191 of the MES server 100 includes a material ordering management department, a material warehousing management department, a material shipping management department, a material warehousing/delivery status department, a material inventory status department, and a material inventory management department.

The Material Order Management Department registers orders before receiving materials. The Material Order Management Department provides management of purchasing locations and the quantity and unit price of purchased materials. The material warehousing management department provides management of material warehousing, including purchase order selection, quantity, and warehouse, through registered material order forms. The Materials Delivery Management Department manages the delivery of incoming materials. At this time, when produced, it is managed by automatic shipment and when registered in material shipment management, it is managed by manual shipment. The material receipt/delivery status section provides the function to check material receipt management and material shipment management at the same time, and also provides the function to enable both registration. In other words, it can provide a combination of the functions of material receipt management and material shipment management. The material inventory status section provides the function to check the current inventory of materials in the warehouse. The Materials Inventory Management Department provides the function to check all information (past to present) on which materials and products have been received. The material inventory management department can provide the same functions as the basic inventory management department.

Hereinafter, each configuration within the intranet server 200 will be described in detail with reference to FIGS. 13 to 16.

Figure 13 is a block diagram showing each configuration of the schedule module 201 according to the present invention.

Referring to FIG. 13, the schedule module 201 of the intranet server 200 includes a monthly schedule, a weekly schedule, a daily schedule, and a schedule list.

Monthly Schedule provides the function to check the monthly schedule calendar and register schedules. The weekly schedule provides the function to check schedules and register schedules on a weekly basis. Daily schedule provides the function to check and register schedules on a daily basis. The schedule list provides the function to check schedule details.

Figure 14 is a block diagram showing each configuration of the work log module 211 according to the present invention.

Referring to FIG. 14, the work log module 211 of the intranet server 200 includes a work log book, a general work log book, a sent log book, a weekly report book, and a received log book.

The work diary provides the function to enable registration of daily and weekly work. The general work log provides a function to check the registered daily work log. The sent logbook provides functions that allow you to designate a recipient when creating a work log and check the sent work log. The weekly reporting department provides functions to enable registration and sharing of weekly reporting data. The reception journal provides a function that allows the designated recipient to check the sender's journal when creating a business journal.

Figure 15 is a block diagram showing each configuration of the electronic payment module 221 according to the present invention.

Referring to FIG. 15, the electronic payment module 221 of the intranet server 200 includes a draft preparation section, a sent document section, an approval setting section, and a progress document section, and the progress document section includes an approval progress document section, an approval public domain, and Includes cooperation department.

The drafting department prepares the draft, sets the approval route, and then approves it. The sent document section provides confirmation of sent documents for approval. The approval setting unit provides settings of approval lines for each person to be approved. The approval progress document department of the progress document department provides confirmation of documents in progress. The approval review section of the progress document section provides a function to enable viewing of documents that have been approved. The cooperation department provides a function so that when a collaborator is selected when drafting, the subject of cooperation can be confirmed.

Figure 16 is a block diagram showing each configuration of the user management module 241 according to the present invention.

Referring to FIG. 16, the user management module 241 of the intranet server 200 includes a user information management unit, a user application approval unit, a department management unit, and a position management unit.

The user information management department provides functions to manage menus and modify information for each user of the intranet. The user application approval department provides the function to approve applications when intranet users apply. The department management department provides functions to register and manage departments. The position management department provides functions to enable registration and management of positions.

Figure 17 is a block diagram showing a smart factory system further including a data management server 300 according to the present invention.

Referring to FIG. 17, the MES server 100 and the intranet server 200 are configured in detail by the data management server 300 to input, register, modify, and delete data and information about the data (hereinafter referred to as ' (referred to as ‘data’) is transmitted. The data management server 300 can provide the received data to the user terminal 10, and the user terminal 10 connects to the data management server 300 and accesses the data stored in the data management server 300. The operation of the smart factory system 1000 according to the invention can be monitored.

Meanwhile, the user holding the user terminal 10 may be an administrator who monitors the operation of the smart factory system 1000 according to the present invention, or a user who has been granted permission from the user application management department and/or the user application approval department. That is, an administrator or user can monitor the operation of the smart factory system 1000 through the user terminal 10, and manage and supervise its operation and use.

There may be a plurality of user terminals 10 according to the present invention, and each user terminal 10 can access data stored in the data management server 300 by connecting to the data management server 300. The data management server 300 receives data received from the MES server 100 and the intranet server 200 and stores it in local storage within the data management server 300.

The user terminal 10 can access the data management server 300 to read, modify, or delete data stored in the data management server 300. Data modified or deleted by one user terminal 10 may be reflected in the data management server 300 and provided to a plurality of user terminals 10 again.

Meanwhile, the data management server 300 according to the present invention may be a centralized storage system including at least one individual server (3110, 3120, 3130, 3140, see FIG. 19). Each individual server 3110, 3120, 3130, and 3140 included in the data management server 300 connects to a storage system connected to a communication network to write or read data. At this time, if a failure occurs in any one of the individual servers (3110, 3120, 3130, 3140) connected to each other, the data in the failed individual server (3110, 3120, 3130, 3140) cannot be used, causing great inconvenience. Therefore, in this specification, the same data is stored redundantly in other individual servers (3110, 3120, 3130, 3140) so that data can be accessed even when a failure occurs in any individual server (3110, 3120, 3130, 3140). ) begins.

Figure 18 is a diagram showing each module of the data management server 300 according to the present invention.

Referring to FIG. 18, the data management server 300 according to the present invention includes a network drive module 320, a data integration management module 310, and a backup module 330. Each module 310, 320, and 330 is connected to each other through a wired or wireless communication network. As an embodiment, the user terminal 10 is connected to the network drive module 320, the network drive module 320 is connected to the data integration management module 310, and the data integration management module 310 is a backup module ( 330).

Figure 19 is a diagram showing each configuration of the data integration management module 310 according to the present invention.

The data integration management module 310 according to the present invention manages data through server duplication with guaranteed high availability (HA) based on virtualization technology. Referring to FIG. 19, the data integration management module 310 includes a plurality of individual servers (3110, 3120, 3130, 3140) and local storage (3111, 3121) included in each individual server (3110, 3120, 3130, 3140). , 3131, 3141). Each individual server (3110, 3120, 3130, and 3140) included in the data integration management module 310 is connected to each other to form a physical network. The data integration management module 310 manages the local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) by grouping (3101, 3102) the local storage (3111) of the same group. , 3121, 3131, 3141) have the same data. That is, the data integration management module 310 groups the local storages 3111, 3121, 3131, and 3141 of each individual server 3110, 3120, 3130, and 3140 through a virtual network and manages them integratedly. The data integration management module 310 redundantly stores identical data in the local storages 3111, 3121, 3131, and 3141 of each group 3101 and 3102 to duplicate servers. The data integration management module 310 immediately provides data stored in other individual servers to the user terminal 10 when a failure occurs in at least one individual server.

For example, the data integration management module 310 may configure the first local storage 3111 of the first server 3110 and the second local storage 3121 of the second server 3120 into the first server group 3101. In one case, each data in the first local storage 3111 and the second local storage 3121 is stored in an alternating manner. That is, when data a is stored in the first local storage 3111 and data b is stored in the second local storage 3121, the data integration management module 310 stores the data a in the first local storage 3111. Data a is copied and stored in the second local storage 3121, and data b from the second local storage 3121 is copied and stored in the first local storage 3111. Accordingly, the first local storage 3111 and the second local storage 3121 of the first server group 3101 store the same data in duplicate. When an inspection or failure of a server occurs, the data integration management module 310 stores the same data in one of the local storages 3111 and 3121 of the first server group 3101, which stores the same data redundantly. 3121), that is, data stored redundantly in the local storage of another server of the same group can be provided to the user terminal 10, so the stability of data use can be guaranteed. A more detailed description of the data integration management module 310 will be provided later.

Figure 20 is a diagram showing each configuration of the network drive module 320 according to the present invention.

Referring to FIG. 20, the network drive module 320 according to the present invention includes a drive agent unit 3211 that provides a network drive to the user terminal 10 and a data integration management module through which the user terminal 10 provides a network drive. It includes a shared storage unit 3213 that allows access to the local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) included in (310). Meanwhile, at this time, the shared storage unit 3213 may be each local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) included in the data integration management module 310. Alternatively, it may be a separate storage where the data of each local storage (3111, 3121, 3131, and 3141) is copied. If the data stored in the shared storage unit 3213 is changed, the data in each local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) is also changed.

That is, the user terminal 10 accesses each local storage (3111, 3121, 3131, 3141) included in the data integration management module 310 through the network drive provided by the drive agent unit 3211 to generate data. When modifications, deletions, etc. are performed, the results are reflected in real time in the data of each local storage (3111, 3121, 3131, 3141) of the shared storage unit (3213) or the data integration management module (310).

Therefore, a plurality of user terminals 10 can share data in each local storage of the data integration management module 310 through a network drive. A more detailed description of the network drive module 320 will be provided later.

Figure 21 is a diagram showing each configuration of the backup module 330 according to the present invention.

Referring to FIG. 21, the backup module 330 according to the present invention is a local storage (3111, 3121, 3131, 3141) in an individual server (3110, 3120, 3130, 3140) managed by the data integration management module 310. Data is backed up according to a preset schedule. The individual servers 3110, 3120, 3130, and 3140 included in the data integration management module 310 further include backup units 3113, 3123, 3133, and 3143, respectively. The backup unit (3113, 3123, 3133, 3143) grants access to data in the local storage (3111, 3121, 3131, 3141) to the backup agent unit (3311) according to a preset backup schedule. The backup module 330 includes a backup agent unit 3311, and the backup agent unit 3311 backs up data in the local storage (3111, 3121, 3131, 3141) according to a preset schedule. (3113, 3123, 3133, 3143) is accessed to back up the data in the local storage (3111, 3121, 3131, 3141) to the backup storage unit (3317).

On the other hand, in server duplication, there is a problem in that data in each local storage (3111, 3121, 3131, and 3141) is stored redundantly in real time, so accidentally reflected data or virus-infected files can also be copied. The backup module 330 can restore accidentally reflected data or virus-infected files by backing up data according to a preset schedule, that is, at intervals. A more detailed description of the backup module 330 will be provided later.

Below, the data integration management module 310, network drive module 320, and backup module 330 according to the present invention will be described in more detail.

The data integration management module 310 according to the present invention is composed of a plurality of individual servers (3110, 3120, 3130, 3140) and a physical switch (not shown). A plurality of individual servers 3110, 3120, 3130, and 3140 form a physical network through a physical switch (not shown). The data integration management module 310 may be implemented with at least two or more servers.

Each individual server (3110, 3120, 3130, 3140) may include hardware such as a central processing unit, memory, and interface device, and software such as an operating system and supervisor. Since the general configuration of server hardware and software is widely known, the following will mainly describe the configuration of the server for the data integration management module 310 of this embodiment.

Each individual server 3110, 3120, 3130, and 3140 may or may not include at least one virtual machine. For example, the first to third servers 3110, 3120, and 3130 may each include at least one virtual machine, and the fourth server 3140 may not include a virtual machine.

As an embodiment, a plurality of individual servers (3110, 3120, 3130, and 3140) integrate and manage the local storage (3111, 3121, 3131, and 3141) included in each individual server (3110, 3120, 3130, and 3140). Includes virtual machines that Hereinafter, a virtual machine that integrates and manages local storage (3111, 3121, 3131, 3141) of multiple individual servers (3110, 3120, 3130, 3140) is referred to as a 'management virtual machine', and other general virtual machines are referred to as 'general'. It is called a ‘virtual machine’.

The management virtual machine is located on at least one of a plurality of individual servers (3110, 3120, 3130, and 3140), and can be migrated between servers as needed.

Each individual server (3110, 3120, 3130, 3140) has at least one general virtual machine (not shown), a management virtual machine (not shown), local storage (3111, 3121, 3131, 3141), and a physical port (not shown). and backup units 3113, 3123, 3133, and 3143. The management virtual machine is located in one of a plurality of servers constituting the data integration management module 310.

Local storage (3111, 3121, 3131, 3141) is a storage medium such as HDD (Hard Disk Drive) or SSD (Solid State Drive) located within individual servers (3110, 3120, 3130, 3140). The local storages 3111, 3121, 3131, and 3141 may include at least one HDD or at least one SSD.

Data of general virtual machines and management virtual machines are stored in local storage (3111, 3121, 3131, 3141).

Since the data of the general virtual machine is stored in the local storage (3111, 3121, 3131, 3141), if an inspection or failure of the individual server (3110, 3120, 3130, 3140) occurs, the data of the individual server (3110, 3120, 3130, 3140) ) There is a problem where the operation of my virtual machine is paused. To solve this problem, in this embodiment, at least two servers are grouped into server groups (3101, 3102) to quickly perform migration of virtual machines and provide uninterrupted virtual machine services, and then grouped into server groups (3101, 3102). ) My data is stored redundantly.

If multiple virtual machines exist within an individual server (3110, 3120, 3130, 3140), a bottleneck may occur in reading/writing data for each virtual machine, or a bottleneck may occur in sending and receiving data to and from a virtual machine on an external server. there is. Alternatively, the management virtual machine needs to quickly process control commands or data to manage local storage (3111, 3121, 3131, 3141) of multiple individual servers (3110, 3120, 3130, 3140) without bottlenecks. For rapid data transmission and reception, this embodiment includes a plurality of physical ports.

The physical ports of individual servers (3110, 3120, 3130, and 3140) are connected to the management virtual machine through a virtual switch (not shown). For example, the management virtual machine can transmit and receive control commands or data for managing the local storage (3111, 3121, 3131, 3141) of multiple individual servers (3110, 3120, 3130, 3140) through a physical port. .

The physical port is connected to the virtual switch to enable data transmission and reception for virtual machine migration. For example, when the first virtual machine located on the first server 3110 migrates to the second server 3120, the virtual machine moves through the physical port of the first server 3110 and the physical port of the second server 3120. Data for machine migration can be transmitted and received.

The physical port is connected to the virtual switch and can transmit and receive data to local storage (3111, 3121, 3131, 3141). For example, data from general virtual machines within individual servers (3110, 3120, 3130, 3140) are transferred to and stored in local storage (3111, 3121, 3131, 3141) through physical ports.

A physical port is connected to at least one general virtual machine through a virtual switch.

The backup units 3113, 3123, 3133, and 3143 are connected to the backup agent unit 3311 of the backup server 3310, which will be described later, and are connected to the individual servers 3110, 3120, 3130, at the request of the backup agent unit 3311. Access rights to data in the local storage (3111, 3121, 3131, 3141) are granted to the backup agent unit 3311 so that data stored in the local storage (3111, 3121, 3131, 3141) of 3140 can be backed up and stored at regular intervals. . The backup unit (3113, 3123, 3133, 3143) can back up all data in the local storage (3111, 3121, 3131, 3141) each time, or can extract and back up only the data that has changed from the previous backup to the current time. A detailed description of the backup units 3113, 3123, 3133, and 3143 and the backup server 3310 will be provided later.

In this embodiment, the general virtual machine and the management virtual machine form a virtual network through a virtual switch. For example, general virtual machines and management virtual machines are assigned private IP (Internet Protocol) addresses used in virtual networks, and each virtual machine can transmit and receive data using the private IP address.

For example, when the data integration management module 310 is composed of two servers, the first server 3110 and the second server 3120, the plurality of servers present in the first server 3110 and the second server 3120 The regular virtual machines and management virtual machines form a virtual network through at least one virtual switch.

The data integration management module 310 includes at least one server group (3101 or 3102), and each server group (3101 or 3102) may be composed of at least two or more individual servers (3110, 3120, 3130, and 3140). . As an embodiment, the data integration management module 310 includes a first server group 3101 including a first server 3110 and a second server 3120, a third server 3130, and a fourth server 3140. ) and consists of a second server group 3102 including.

As another example, the number of servers included in each server group may be different. For example, the first server group may be composed of two servers, and the second server group may be composed of three servers.

The management virtual machine integrates and manages multiple server local storages (3111, 3121, 3131, and 3141) according to the grouping information of the server group. For example, the management virtual machine determines the resource information of the local storage (3111, 3121, 3131, 3141) of the first to fourth individual servers (3110, 3120, 3130, 3140) and then stores it in one integrated storage (3111, 3121, 3131, 3141).

As an embodiment, the management virtual machine stores the data of the general virtual machine redundantly in the local storage (3111, 3121, 3131, 3141) within the server group (3101, 3102). For example, if there is a data write request from the first virtual machine located in the first server 3110 of the first server group 3101, the management virtual machine sends the data corresponding to the data write request of the first virtual machine to the first server group 3101. Not only is it stored in the first local storage 3111 of the first server 3110 where the virtual machine is located, but also the second local storage of the second server 3120 that exists in the same server group 3101 as the first server 3110 ( 3121).

As another example, the management virtual machine may store the metadata of the general virtual machine and the management virtual machine redundantly within the server groups 3101 and 3102. For example, metadata for the first virtual machine of the first server 3110 is stored in the first local storage 3111 of the first server 3110 and the second local storage 3121 of the second server 3120. It is stored redundantly. For example, when a virtual machine is created on each individual server (3110, 3120, 3130, 3140), each individual server (3110, 3120, 3130, 3140) is within the same server group (3101, 3102) according to server grouping information. Virtual machine meta information can be stored redundantly in each local storage (3111, 3121, 3131, and 3141).

Since the general data and metadata of each virtual machine within the server group (3101, 3102) are stored redundantly, migration of the virtual machine within the server group (3101, 3102) can be performed quickly.

As an embodiment, the integrated storage (3111, 3121, 3131, 3141), which integrates the local storage (3111, 3121, 3131, 3141) of a plurality of individual servers (3110, 3120, 3130, 3140), includes a general virtual machine and General data and metadata of the management virtual machine are stored. General data refers to various data generated from virtual machine services, and metadata refers to various data that defines a virtual machine, such as virtual machine identifier, virtual machine IP address, and operating system. General data and metadata are redundantly stored in at least two server local storages (3111, 3121, 3131, and 3141) for each server group (3101, 3102).

As an embodiment, the data integration management module 310 includes one server group 3101, and the server group 3101 includes a first server 3110 and a second server 3120. A management virtual machine and first and second general virtual machines exist in the first server 3110, and third and fourth general virtual machines exist in the second server 3120.

Virtual machine migration may occur in the event of server maintenance or failure. For example, the management virtual machine can periodically send a ping signal to each server to check which server is experiencing a failure.

As an embodiment, when there is an inspection request for the first server 3110 or a failure occurs, the management virtual machine is first migrated from the first server 3110 to the second server 3120. And the first and second general virtual machines of the first server 3110 are migrated from the first server 3110 to the second server 3120. Since data is stored redundantly in the local storages (3111, 3121) of the first server (3110) and the second server (3120), migration can be completed quickly without separate data transmission and reception, enabling uninterrupted provision of virtual machine services. do.

When the inspection of the first server 3110 is completed or the problem is resolved, the general virtual machine can be migrated back to the first server 3110. At this time, since the data of the general virtual machine remains in the first server 3110, only data newly stored by the general virtual machine in the second server 3120 can be transmitted to the first server 3110.

As an embodiment, the first server group 3101 consists of the first server 3110 and the second server 3120, and the second server group 3102 consists of the third server 3130 and the fourth server 3140. ), and when the first server group (3101) is inspected or a failure occurs, the management virtual machine and general virtual machine existing in the first server group (3101) are each server (3130, Data migrated to 3140) and stored in local storages 3111 and 3121 of the first server group 3101 are stored in local storages 3131 and 3141 of the second server group 3102.

When the inspection of the first server group 3101 is completed or the problem is resolved, the general virtual machine can be migrated back to the first server group 3101. At this time, since the data of the general virtual machine remains in the first server group 3101, only data newly stored by the general virtual machine in the second server group 3102 can be transmitted to the first server group 3101.

Next, the network drive module 320 according to the present invention will be described.

The network drive module 320 according to the present invention includes a network drive server 3210, and the network drive server 3210 includes a drive agent unit 3211 and a shared storage unit 3213 as described above. .

Meanwhile, the network drive server 3210 can be connected to a plurality of user terminals 10 through a wired or wireless communication network. Additionally, the network drive server 3210 may be connected to each individual server 3110, 3120, 3130, and 3140 of the data integration management module 310.

The user requests a connection to the network drive server 3210 using the user terminal 10, and the user terminal 10 connects to each storage or shared storage unit of the shared storage unit 3213 included in the network drive server 3210. Data in the local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) included in the data integration management module (310) connected to (3213) can be provided and used as a network drive. .

The network drive server 3210 includes a drive agent unit 3211 and a shared storage unit 3213.

The drive agent unit 3211 transmits and receives data between the network drive server 3210 and a plurality of user terminals 10. The shared storage unit 3213 includes a storage space provided as a network drive according to the user of the user terminal 10, and the storage space at this time is stored in each individual server 3110, 3120, and 3120 included in the data integration management module 310. It may be a local storage (3111, 3121, 3131, 3141) of 3130, 3140). Hereinafter, the description will be made assuming that the data stored in the local storage (3111, 3121, 3131, 3141) is stored in the shared storage unit 3213, but the shared storage unit 3213 itself is stored in the data integration management module 310 described above. It can also be interpreted to mean each local storage (3111, 3121, 3131, 3141).

The user terminal 10 according to the present invention is a typical computing terminal used by a user, such as a PC, laptop, netbook, tablet PC, PDA, mobile, or smartphone. The user terminal 10 is equipped with a local storage medium (not shown) for storing data, and a local operating system (OS, not shown) for the terminal is installed and operated in the user terminal 10.

The local operating system (OS) for the terminal provides a data explorer to explore data such as data stored in the local storage medium for the terminal. Data Explorer is a window-type GUI (graphical user interface) type explorer that displays the directory structure in a folder-type hierarchy. Additionally, the local operating system (OS) for the terminal mounts the storage medium as a drive and allows data to be searched using a directory structure.

In other words, in addition to the local storage medium for the terminal, external storage media or storage space on the network can be mounted as a drive. In general, when a storage medium of another computer terminal connected on a network is connected as a drive, it is called a network drive.

The network drive server 3210 according to the present invention provides data in local storages 3111, 3121, 3131, and 3141 stored in the shared storage unit 3213 or connected to the shared storage unit 3213 to the user terminal 10. do.

The network drive server 3210 allows multiple users to perform collaborative work by sharing one data. In other words, when one user checks out the data to use it, the data is set to locked to prevent other users from modifying the data. Additionally, when a user finishes using the data and checks in, the lock state of the data is released so that other users can use and modify the data.

The network drive server 3210 stores and manages data in the shared storage unit 3213. The shared storage unit 3213 includes a known database, storage, and/or repository.

Meanwhile, data stored or connected to the shared storage unit 3213 is managed and accessed through the network drive server 3210, or is stored in each local storage unit 3111, 3121, and As 3131 and 3141) are approached, data will be stored and managed in the network drive server 3210 without mention of the shared storage unit 3213.

The network drive server 3210 according to the present invention further includes a drive agent unit 3211 that allows the user terminal 10 to access data managed by the network drive server 3210.

In particular, the drive agent unit 3211 allows the shared storage unit 3213 to be accessed in the form of a network drive from the user terminal 10. To this end, the drive agent unit 3211 converts the data stored in the shared storage unit 3213 into the data system of the operating system of the user terminal 10 (or local operating system for the terminal). The drive agent unit 3211 mounts the converted data system as a network drive of the local operating system for the terminal and provides it. In other words, the drive agent unit 3211 provides a data sharing server function that can share data with the user terminal 10 through a network drive of the local operating system for the terminal.

The network drive server 3210 converts the data stored in the shared storage unit 3213 to correspond to the data system structure of the local operating system for the terminal provided by the user terminal 10. In detail, the drive agent unit 3211 requests the shared storage unit 3213 for a list of data stored in the shared storage unit 3213 and receives the list of data. The received data list is assigned a unique identifier (or data ID) for each data, and when specific data is selected, the contents of the specific data can be requested and received from the shared storage unit 3213 through the unique identifier of the specific data. .

The terminal local operating system of the user terminal 10 uses a data sharing protocol to share data stored in the shared storage unit 3213 connected to the network. At this time, the data sharing protocol is a protocol for handling data stored in another computer terminal through the same interface as the data explorer of one's computer terminal. That is, when the user terminal 10 mounts the shared storage unit 3213 as a drive through the data sharing protocol, data can be managed through the same interface as if a local storage medium for the terminal were mounted. As an example, when the local operating system for the terminal is Microsoft's Windows, the data sharing protocol is the Samba (SMB) protocol.

The drive agent unit 3211 provides a data sharing server function according to the data sharing protocol, requests mount of the shared storage unit 3213 from the user terminal 10 to the drive agent unit 3211, and drives the drive agent unit 3211. ) mounts a network drive with a data system structure corresponding to the data list.

The user terminal 10 includes an interface unit 11 that extends the shell of the data explorer of the local operating system for the terminal. The interface unit 11 processes the unique functions of the network drive server 3210 in addition to the data system functions of the local operating system for the terminal. In other words, it processes the data collaboration performance function of the network drive server 3210 described above.

The shell of the data explorer of the local operating system for the terminal is an interface program for processing user commands. For example, when you double-click a specific folder in the data explorer using the shell, you move to that folder, or when you select specific data or folder, a context menu related to the selected data is displayed.

The interface unit 11 extends the shell of the data explorer and receives information about data sharing (hereinafter referred to as sharing information) from the drive agent unit 3211 and displays it as a context menu. Additionally, the extended shell provided by the interface unit 11 performs tasks such as displaying the lock status as a context menu when data is being edited by another user, or briefly displaying all version information of the data.

Additionally, the extended shell displays the unique functions of the network drive server 3210 as a context menu, and when the menu is selected from the context menu, the command is transmitted to the drive agent unit 3211. The drive agent unit 3211 interprets the command and transmits necessary data to the user terminal 10 according to the command.

Meanwhile, when shared information is received from the drive agent unit 3211 in the extended shell, the shared information is transmitted and received by the data sharing protocol. If the local operating system for the terminal is Microsoft's Windows, shared information is transmitted by an NTFS stream, a type of alternate data stream (ADS).

The drive agent unit 3211 establishes a data sharing session with the user terminal 10 through a data sharing protocol and shares data in the form of a local data system. That is, the drive agent unit 3211 shares data in the shared storage unit 3213 of the network drive server 3210 in the form of a local data system.

As explained earlier, the data sharing protocol is a protocol for handling data stored in other computer terminals through the same interface as the data explorer of one's own computer terminal. When a storage medium connected to the network is mounted as a drive, it is as if it were a local storage medium for the terminal. You can manage data using the same interface as the mounted one. If the local operating system for the terminal is Microsoft's Windows, the data sharing protocol is the Samba (SMB) protocol.

The drive agent unit 3211 functions as a data sharing server according to the data sharing protocol. In the case of Windows, the drive agent unit 3211 performs the function of a SMB server, mounts the data of the network drive server 3210 in the form of a network drive and shares it as shared data on the network. That is, the drive agent unit 3211 connects the data sharing session to the network drive.

The drive agent unit 3211 transmits information regarding data sharing (hereinafter referred to as sharing information) to the interface unit 11 and receives a command regarding data sharing (hereinafter referred to as sharing command) from the interface unit 11.

The interface unit 11 displays data sharing information as a data context menu. At this time, the sharing information includes a sharing command, and the interface unit 11 transmits the sharing command selected by the context menu to the drive agent unit 3211.

Next, we explain the data sharing function among the unique functions of data management. Functions for sharing data include functions such as check-in/check-out and data locking.

When data is modified, it is stored by version by the network drive server 3210. The interface unit 11 displays version-specific information about data as shared information.

When a specific version of the data is selected in the interface unit 11 and requests to be received, the drive agent unit 3211 loads the specific version of the data stored in the network drive server 3210 and sends it to the user terminal 10. send.

Data can be shared by multiple users and modified by each user. At this time, if multiple users modify and save data at the same time, only the data of the user who finally saved may be saved, and the data of other users may not be saved. Therefore, only one user should be able to modify data at a specific time. For this purpose, check-in/check-out is provided.

The drive agent unit 3211 sets the data to a locked state where it cannot be modified when the checkout sharing command is selected among the data sharing information through the interface unit 11, and locks the data when the checkin sharing command is selected. ) Release the state. In other words, when data is set to a locked state, subsequent users cannot access the data, and when a user issues a checkout command for specific data, the data is locked. Therefore, other users cannot view specific data. When the user completes modifying the data, he or she saves the data.

Meanwhile, as described above, when an inspection or failure occurs in any of the individual servers 3110, 3120, 3130, 3140 included in the data integration management module 310 containing the data desired by the user, that is, for example, , the data a that the user wants to access is located in the first local storage 3111 of the first server 3110, and the interface unit 11 of the user terminal 10 is connected to the drive agent unit 3211 by the first server 3110. ), and when sending a data reception request signal, if an inspection or failure occurs in the first server 3110, the drive agent unit 3211 is connected to the shared storage unit 3213. Data a contained in the second local storage 3121 of the second server 3120, which is in the same server group 3101 as the first server 3110, rather than the first server 3110, can be provided to the user terminal 10. there is. Therefore, the data management server 300 according to the present invention can guarantee the stability of data use.

Next, the backup module 330 according to the present invention will be described.

The backup module 330 according to the present invention includes a backup server 3310, and the backup server 3310 includes a backup agent unit 3311 and a backup storage unit 3317, as described above.

The backup agent unit 3311 includes a backup program, and when the backup program is executed, the backup target in the local storage (3111, 3121, 3131, 3141) of the individual server (3110, 3120, 3130, 3140) according to a preset schedule. Data is designated and formed as backup data based on the designated backup target data. The backup agent unit 3311 transmits the formed backup data to the backup storage unit 3317. Meanwhile, the backup program may be provided and executed on the user terminal 10 or may be automatically executed by the backup unit 3113, 3123, 3133, and 3143 of the data integration management module 310. As the backup program is provided to the user terminal 10, the user terminal 10 can specify a backup schedule through the backup program. Meanwhile, the backup program is provided through an administrator terminal (not shown) owned by a separate server administrator, and a backup schedule may be specified by the administrator terminal. Additionally, when the backup program is executed by the backup unit (3113, 3123, 3133, 3143), the backup schedule can be automatically specified by the backup unit (3113, 3123, 3133, 3143). Backup schedule designation for the backup units 3113, 3123, 3133, and 3143 will be described later.

The backup target data is data created, deleted, and modified by the user terminal 10 or individual servers (3110, 3120, 3130, 3140) and is stored within the user terminal 10 or individual servers (3110, 3120, 3130, 3140). It can be a data file that can be processed in .

The backup storage unit 3317 receives and stores backup data from the individual servers 3110, 3120, 3130, and 3140 through the backup agent unit 3311.

When storing backup data, the backup storage unit 3317 creates a copy of the backup data and stores it separately from the original to prepare for the case where the original backup data is damaged or cannot be used.

The backup server 3310 executes backups according to a set schedule, detects whether the set capacity among the accumulated backup data is exceeded, compares the creation date of the backup data, and deletes the excess capacity portion of the data created first to spare. By designing it to continuously secure disk space, it automatically performs backups after the data management server 300 is in operation, and when disk space is insufficient due to accumulated data, disk space is secured by automatically determining whether the set capacity has been exceeded.

The backup server 3310 generates a plurality of backup data and stores them individually so that the original data can be selectively recovered from the accumulated backup data even if the corresponding backup data is damaged.

Figure 22 is a diagram showing each configuration of the backup agent unit 3311 according to the present invention.

Referring to FIG. 22, the backup agent unit 3311 includes a backup memory unit 3312, a backup input unit 3313, a backup control unit 3314, and a backup display unit 3315.

In the backup memory unit 3312, the backup program provided to the user terminal 10, the administrator terminal, or the backup unit 3113, 3123, 3133, and 3143 is stored, and is received from the user terminal 10 or the administrator terminal or is stored in the backup unit. Settings such as the backup schedule automatically set by (3113, 3123, 3133, 3143), multiple backup data folders, backup pre-task processor, backup post-task processor, and whether to terminate the backup after completion are saved.

The backup input unit 3313 receives the backup program execution command, backup time, process or service to be terminated before running the backup program, and operation of the backup program from the user terminal 10 or the backup unit (3113, 3123, 3133, 3143). It receives a process or service to be executed after termination, a predetermined number of folders for storing backup data, and whether the backup agent unit 3311 will be automatically terminated after backup.

The backup control unit 3314 reads the backup program execution command and backup schedule received by the backup input unit 3313 from the user terminal 10, the administrator terminal, or the backup unit 3113, 3123, 3133, and 3143, and executes the backup schedule according to the read schedule. Accordingly, the backup target data within the individual servers (3110, 3120, 3130, and 3140) is designated, the designated backup target data is formed as backup data, and the formed backup data is delivered to the backup storage unit 3317.

As an embodiment, when forming designated backup target data into backup data, the backup control unit 3314 not only forms the original backup target data into backup data, but also compresses the backup target data to form backup data. By reducing the capacity of the backup data and delivering it to the backup storage unit 3317, the storage space of the backup storage unit 3317 can be utilized more efficiently. The backup control unit 3314 allocates a permanent memory space for permanently storing backup data and a general memory space for storing backup data other than permanent storage to the backup storage unit 3317, and checks whether the formed backup data is permanently stored. And, if the created backup data needs to be stored permanently, it is stored in a permanent memory space.

As an embodiment, the backup control unit 3314 exceeds the set capacity of the backup data accumulated in the backup storage unit 3317, and when deleting the excess portion, only the backup data stored in the general memory space is deleted and the backup data stored in the permanent memory space is deleted. By not deleting backup data separately stored in , it is possible to prevent data that must be retained by the user from being deleted.

The backup display unit 3315 displays the operating status of the backup program run by the backup control unit 3314 on the display device of the user terminal 10 or the administrator terminal.

As an embodiment, the backup display unit 3315 displays the operating status of the backup program on the taskbar on the user terminal 10 or the administrator terminal (for example, in the case of a Windows PC, the taskbar at the bottom of the screen, etc.). It can be displayed.

As an embodiment, the backup display unit 3315 displays a settings window for entering settings for the backup program (for example, backup time or a process or service to be terminated before running the backup program, etc.) on the user terminal (10). ) can be displayed on the display device.

As an embodiment, the backup display unit 3315 displays the backup program to the user through a pop-up window (i.e., a new window that is suddenly created to display certain contents of a specific website) after the backup program starts or ends. Not only can the driving status be informed by visual means, but also by auditory means through sound reproduction means (for example, external speakers or built-in speakers, etc.) provided in the user terminal 10 or the administrator terminal. The running status of the backup program can also be notified to the user.

The backup control unit 3314 transmits backup data to the backup storage unit 3317.

The backup control unit 3314 sets a standard capacity for deleting the backup data previously stored in the backup storage unit 3317 and stores it in the backup memory unit 3312, and stores the backup data stored in the backup storage unit 3317. The capacity is read, and the reference capacity read from the backup memory unit 3312 is compared with the capacity of the backup data stored in the backup storage unit 3317. As a result of the comparison, the backup control unit 3314 determines that when the capacity of the backup data stored in the backup storage unit 3317 exceeds the standard capacity, the backup data created first among the backup data stored in the backup storage unit 3317 exceeds the set capacity. You can delete as much as one part.

As an embodiment, the backup control unit 3314 determines that the capacity of the backup data stored in the backup storage unit 3317 is set to a certain percentage of the available storage capacity of the backup storage unit 3317 (for example, the amount of backup data stored in the backup storage unit 3317 When the available storage capacity (80%) is exceeded, the creation date among the backup data stored in the backup storage unit 3317 is compared and the portion of the data created earlier that exceeds the capacity is deleted, so that the backup storage unit 3317 It can be used to create available storage space for newly incoming backup data.

As an embodiment, when deleting backup data stored in the backup storage unit 3317, the backup control unit 3314 deletes a predetermined capacity (for example, 10% of the available storage capacity of the backup storage unit 3317, etc.) The backup storage unit 3317 can secure available storage space for the newly incoming backup data by deleting or deleting an amount equivalent to the newly incoming backup data capacity.

As an embodiment, the backup control unit 3314 stores data other than backup data in the backup storage unit 3317 (for example, video data or image data stored according to the needs of a user or administrator). , By reading the standard capacity based on the combined capacity of data other than backup data and the backup data, it is possible to prevent the case where available storage space for newly incoming backup data becomes insufficient.

When the backup time is input from the backup input unit 3313 and a backup time reservation request is received, the backup control unit 3314 sets the backup time input according to the backup time reservation request in the backup memory unit 3312.

As an embodiment, the backup control unit 3314 can provide work convenience by allowing the backup program to run at the same time every day when setting the backup time.

When the backup control unit 3314 receives a designated folder name for storing backup data in a pre-designated folder from the backup input unit 3313 and receives a request for designated backup settings, the backup control unit 3314 returns the designated folder name entered according to the designated backup setting request. Set in the backup memory unit 3312.

When performing a designated backup, the backup control unit 3314 can store separate backup data for each designated folder and can also allow each folder to be backed up at a different time.

The backup control unit 3314 performs a backup operation of a designated data folder and then adds the date and time to the set value of the folder name where the backup data is stored and stores it, thereby preventing the same folder name from being used during daily cumulative backup and preventing the user from using the same folder name. When restoring backed up data, you can selectively restore it by distinguishing the date and time the backup was created.

When the backup control unit 3314 receives a plurality of folder names for storing a predetermined number of backup data in a predetermined folder from the backup input unit 3313 and receives a request for setting up multiple backups, the backup control unit 3314 responds to the request for setting up multiple backups. Multiple input folder names can be set in the backup memory unit 3312.

Meanwhile, the backup unit (3113, 3123, 3133, 3143) according to the present invention analyzes the load of each individual server (3110, 3120, 3130, 3140) according to the data management server 300 according to the present invention, and stores the data. A backup schedule can be specified by inputting the day and time of day when the management server 300 has the least load into the backup input unit 3313.

At this time, the server load analysis of the backup unit (3113, 3123, 3133, 3143) is, for example, the number of user terminals 10 connected to each server of the data integration management module 310 through the network drive module 320. Alternatively, the number of data request messages sent by the interface unit 11 of the user terminal 10 to the drive agent unit 3211 may be comprehensively analyzed. At this time, the number of connected user terminals 10 and the number of data request messages may be derived by analyzing the log in the data management server 300.

The backup units 3113, 3123, 3133, and 3143 continuously analyze the degree of past server load and transmit the analysis results to the backup control unit 3314.

Figure 23 is a diagram showing an embodiment of a server load diagram according to the present invention.

Referring to FIG. 23, the backup control unit 3314 organizes the degree of server load received from the backup units 3113, 3123, 3133, and 3143 in the form of a plurality of cells divided by day of the week and time zone to determine the server load. create a diagram At this time, the cell may be in the form of a plurality of consecutive squares. The server load diagram generated by the backup control unit 3314 may be displayed on the user terminal 10 or the administrator terminal by the backup display unit 3315 and provided to the user or administrator.

The backup control unit 3314 can display a plurality of cells differently depending on the degree of server load. For example, when the server load is low, the cells are colored darkly, and when the server load is large, the cells are colored lightly to display the backup. Unit 3315 can be displayed on the user terminal 10. Meanwhile, the coloring of cells according to each day and time of the server load diagram may have a coloring value according to the degree of server load corresponding to the average value of the degree of server load for days and times of multiple weeks. Alternatively, the server load diagram according to one embodiment may represent the degree of server load in the form of a square pillar with the aforementioned cell as the bottom, and in this case, the degree of server load may be the height of the square pillar. The backup display unit 3315 can display a server load diagram with square column-shaped cells on the user terminal 10.

Meanwhile, in Figure 23, the horizontal length of each cell is shown to mean 1 hour as an example. For convenience, only the time from midnight to noon is shown from 0:00 a.m. to 12:00 a.m., but the server load is also The shape of each cell can be changed at any time depending on the embodiment. Meanwhile, the backup units 3113, 3123, 3133, and 3143 can track and analyze not only the past server load, but also the time required for backup.

The backup control unit 3314 generates a straight line connecting the centers of cells according to the time zone with the lowest load for each day of the week in the server load chart organized in the form of a plurality of cells, and calculates the length of the generated straight line. .

If the time required to back up data in the data management server 300 according to the present invention ends within the time of a single cell, as an example, within one hour, such as the horizontal length of the cell shown in FIG. 23, the backup control unit ( 3314) determines that past backup times did not take long.

If it is determined that the backup time will not take long, the backup control unit 3314 selects the day and time zone with the shortest length among the lengths of the straight line connecting the center of the cell corresponding to the low load time zone, and selects the day and time zone. You can execute a backup by automatically specifying a backup schedule by entering it into the backup input unit 3313.

For example, as shown in Figure 23, the length of the line segment connecting the center of each cell at 5 AM on Tuesday and Wednesday is 1, and the length of the line segment connecting the center of each cell at 4 AM on Thursday and Friday is 1. If is 1, you can specify a backup schedule to perform backups at 5 a.m. on Tuesdays and Wednesdays and at 4 a.m. on Thursdays and Fridays.

If the past backup time does not take a long time, the backup control unit 3314 finds the length of a line segment connecting consecutive low-load times and selects the one with the shortest length. This is because if the same time zone with a short distance is continuous, the accuracy can be guaranteed that the load in that time zone is low.

Meanwhile, the backup input unit 3313 can receive the backup time zone from the user terminal 10 or the administrator terminal, and the backup time zone input from the user terminal 10 or the administrator terminal is the same according to the operation of the backup control unit 3314. When a line segment of length is derived, the time zone closest to the input backup time zone can be designated as the backup schedule. That is, if the backup time input from the user terminal 10 or the administrator terminal is 2 AM, backup is performed between 5 AM on Tuesday and Wednesday and 4 AM on Thursday and Friday when the line segment length is 1, as shown in Figure 23. The control unit 3314 can specify a backup schedule by specifying the backup time as 4 a.m. on Thursday and Friday. In this way, if the backup time zone is input from the user terminal 10 or the administrator terminal and one of the days and time zones with the same line segment length is selected, the backup schedule can be set to perform backup at the specified time zone on other days of the week, that is, at 4 am. You can.

On the other hand, unlike the above, if the time required to back up data in the data management server 300 does not end within the time of a single cell, as an example, within one hour according to the horizontal length of the cell shown in FIG. 23 , the backup control unit 3314 determines that the past backup time took a long time.

Figure 24 is a diagram showing another embodiment of a server load diagram according to the present invention.

In this case, when it is determined that the past backup time took a long time, the backup control unit 3314, referring to FIG. 24, calculates the distance of the line segment connecting the centers of the cells in the continuous low-load time zone. This is because the longer the length of the line segment obtained by the backup control unit 3314, the less load can be placed on each individual server (3110, 3120, 3130, and 3140) within the data management server 300 due to backup.

When the backup control unit 3314 continuously selects cells in the time zone with the lowest load, it first derives the cell in the time zone with the lowest load on each day of the week, and then derives the cell in the time zone with the lowest load after that cell. At this time, when the cell in the lowest load time zone and the cell in the next lowest load time zone are adjacent to each other, the backup control unit 3314 connects the centers of the two adjacent cells. Again, the backup control unit 3314 derives the cell in the next low-load time period and determines whether the derived cell is adjacent to both cells whose centers are connected by a line segment. If the derived cell is adjacent to both cells whose centers are connected by a line segment, the centers are connected again, and if it is not adjacent to both cells, the backup control unit 3314 no longer derives the low-load time for the corresponding day of the week.

As described above, when the backup time takes a long time, the center of each cell derived by the backup control unit 3314 is connected as shown in FIG. 24. At this time, the backup control unit 3314 derives how long the past backup time took, and compares the derived backup time with the length of the line segment connecting the center of each cell. If the derived backup time is 2 to 3 hours, in order to minimize the load on each individual server (3110, 3120, 3130, 3140) within the data management server 300 due to backup, backup is performed on Wednesday and Friday of FIG. 24. excluded from the schedule. This is determined to be excluded because the length of the line segment between the centers of each cell on Wednesday and Friday in FIG. 24 is 2. In addition, 2 AM to 6 AM on Monday, 2 AM to 5 AM on Tuesday, 3 AM to 6 AM on Thursday, and 9 AM to Saturday, including all 2 to 3 hours of the derived backup time. The backup control unit 3314 specifies a backup schedule so that backups are performed at 12:00 AM and between 5:00 AM and 11:00 AM on Sundays, respectively.

Meanwhile, as described above, the backup input unit 3313 can receive a backup time zone from the user terminal 10, and the time zone at which the backup starts can be determined according to the backup time zone input from the user terminal 10. For example, if the backup time input from the user terminal 10 is 2 a.m., backup starts at 2 a.m. on Monday and Tuesday, and on Thursday, backup starts at 3 a.m. closest to the input time zone. Backups can start at 9:00 AM on Saturdays and 5:00 AM on Sundays. On the other hand, if the backup time input from the user terminal 10 is 7 a.m., the backup starts at 3 a.m. on Monday so that the backup can be completed at the time closest to 7 a.m., and on Tuesday the backup starts at 2 a.m. The backup schedule can be set to start at 3:00 AM on Thursday, 9:00 AM on Saturday, and 5:00 AM on Sunday.

Figure 25 is a diagram showing another embodiment of a server load diagram according to the present invention.

Meanwhile, the horizontal length of the cell within the server load may change depending on the time zone input from the user terminal 10 or the administrator terminal. In other words, a weight can be given to the horizontal length of the cell according to the time zone input by the user terminal 10 or the administrator terminal. For example, if the time zone entered by the user terminal 10 or the administrator terminal is 5 a.m., the horizontal length corresponding to 5 a.m. in the server load may be modified to be twice that amount. When the horizontal length is changed like this, the length of the line segment passing through the center of the cell corresponding to 5 AM is also given a weight of 2, which is an increase of 1. For example, as shown in FIG. 25, as the horizontal length of the cell corresponding to 5 a.m. is doubled, the length of the line segment connected to the center at 5 a.m. also increases, and the backup control unit 3314 increases in length. The above-described calculation is performed based on the line segment. Therefore, the backup schedule can be specified in consideration of the time zone input from the user terminal 10 or the administrator terminal. In the case of Friday, because the length of the line segment was 2 in FIG. 24, backup was not performed on Friday. As in FIG. 25, Likewise, as the horizontal length of the cell corresponding to 5 a.m. increases, the line segment length for Friday becomes 3, so the backup schedule can be changed so that backup is performed on Friday as well.

Meanwhile, the time zone input from the user terminal 10 or the administrator terminal can receive multiple time zones with priorities, and each time zone has a horizontal length of 5 times, 4 times, 3 times, 2 times, etc. depending on the priority. After lengthening, a backup schedule can be specified according to the length of the line segment connecting the center of each cell.

The backup control unit 3314 may check whether the backup program stored in the backup memory unit 3312 is genuine when executing the backup program, and may stop execution of the backup program if the backup program is not genuine.

When executing a backup program, the backup control unit 3314 reads a specific key value stored in the backup storage unit 3317 and compares it with the key value of the backup program stored in the backup memory unit 3312. If the two compared values are different, In this case, an error message is displayed and the execution of the backup program is stopped, preventing illegal copying of the backup program and protecting the rights of the program developer.

The backup control unit 3314, which has the above-described configuration, can store the characteristic key value of the hard disk to determine whether the program is genuine and determine whether to execute it to protect copyright.

The user terminal 10 or administrator terminal according to the present invention is a terminal such as a desktop PC, laptop PC, tablet PC, or smartphone equipped with an input means such as a keyboard, mouse, touchpad, or touch screen, and a display screen. It is not limited, and it is possible to connect to the data management server 300 and/or the network drive server 3210 of the network drive module 320 through a communication network, input search information and selection information, and display search result information. Any configuration that can process digital information that can install an application program can be included. The user terminal 10 or administrator terminal according to the present invention is a component that connects to the data management server 300 or the network drive server 3210 through a communication network to transmit and receive information, for example, a smartphone or tablet. PC (tablet personal computer), mobile phone, video phone, desktop PC (desktop personal computer), laptop PC (laptop personal computer), netbook computer, PDA (personal digital assistant), PMP (portable multimedia player) ), wearable device (e.g., smart glasses, head-mounted-device (HMD), etc.), unmanned terminal (kiosk), or smart watch). there is.

The user terminal 10, administrator terminal, MES server 100, intranet server 200, data management server 300 and their respective detailed components according to the present invention can communicate through the communication unit and communication network provided by each. . A communication network refers to a connection structure that allows information exchange between nodes such as terminals and servers. Examples of such communication networks include the 3rd Generation Partnership Project (3GPP) network, Long Term Evolution (LTE) network, and 5G. Network, WIMAX (World Interoperability for Microwave Access) network, Internet, LAN (Local Area Network), Wireless LAN (Wireless Local Area Network), WAN (Wide Area Network), PAN (Personal Area Network), wifi network, It includes, but is not limited to, a Bluetooth network, satellite broadcasting network, analog broadcasting network, and DMB (Digital Multimedia Broadcasting) network. The communication unit provided by the user terminal 10, administrator terminal, MES server 100, intranet server 200, data management server 300 and their respective detailed components is capable of performing wired and wireless data communication through the above-described communication network. It may include electronic components provided for the communication network.

In this specification, the MES server 100, intranet server 200, data management server 300, and their respective detailed components may be processors that execute sequential execution processes stored in memory. Alternatively, they may operate as software modules driven and controlled by a processor. Furthermore, a processor may be a hardware device.

The first to fourth local storage units 3111, 3121, 3131, and 3141, the shared storage unit 3213, and the backup storage unit 3317 according to the present invention may include a database management system (hereinafter referred to as DBMS). DBMS is a set of software tools that allow multiple users to access data in a database. DBMS includes IMS, CODASYL DB, DB2, ORACLE, INFORMIX, SYBASE, INGRES, MS-SQL, Objectivity, O2, Versanat, Ontos, Gemstone, Unisql, Object Store, Starburst, Postgres, Tibero, MySQL or MS-access. can do. DBMS allows access to specific data depending on the input of a specific command.

In this specification, 'part' includes a unit realized by hardware, a unit realized by software, and a unit realized using both. Additionally, one unit may be realized using two or more pieces of hardware, and two or more units may be realized using one piece of hardware.

The scope of protection of the present invention is not limited to the description and expression of the embodiments explicitly described above. In addition, it is to be added once again that the scope of protection of the present invention may not be limited due to changes or substitutions that are obvious in the technical field to which the present invention pertains.

10: user terminal 11: interface unit
100: MES server 101: Standard information management module
111: Sales management module 121: Quality management module
131: Equipment management module 141: Test management module
151: Sample management module 161: System management module
171: Monitoring module 181: Production management module
191: Material management module 200: Intranet server
201: Schedule module 211: Work log module
221: Electronic payment module 231: Notice module
241: User management module 300: Data management server
310: Data integration management module 3101: 1st server group
3102: 2nd server group 3110: 1st server
3111: first local storage 3113: backup unit
3120: Second server 3121: Second local storage
3123: Backup unit 3130: Third server
3131: Third local storage 3133: Backup unit
3140: Fourth server 3141: Fourth local storage
3143: Backup unit 320: Network drive module
3210: Network drive server 3211: Drive agent unit
3213: Shared storage unit 330: Backup module
3310: Backup server 3311: Backup agent unit
3312: Backup memory unit 3313: Backup input unit
3314: Backup control unit 3315: Backup display unit
3317: Backup storage unit 1000: Smart factory system

Claims (5)

In the smart factory system,
The smart factory system includes an MES server,
The MES server is,
A standard information management module that manages information that becomes the standard of the smart factory system;
A sales management module that registers and manages information related to product sales;
Quality control module that registers and manages documents related to product quality;
Equipment management module that registers and manages information related to the import/exit, repair and calibration of equipment;
A test management module that registers and manages information related to the test process;
A sample management module that registers and manages information related to received and registered samples;
A system management module that registers and manages information related to the operation of the smart factory system;
Monitoring module that registers and manages information within the testing laboratory;
A production management module that registers and manages information related to manufactured products; and
Material management module that registers and manages information on ordering and receipt of materials;
Smart factory system including. In claim 1,
The standard information management module is,
Includes item management department, BOM management department, quotation management department, employee management department, business trip management department, business partner management department, transaction history management department, certificate management department, customer management department, business management department, meeting minutes department, material management department, product management department, process management department, and basic inventory management department,
The sales management module is,
Test quotation management department, transaction history status department, consultation schedule calendar department, consultation schedule status department, contract management department, customer management department, performance management department, A/S management department, A/S processing status department, customer request deadline management department, product order management department and product Includes the quotation management department,
The quality control module is,
It includes the Quality Document Management Department, Quality Document Record Management Department, KOLAS Meeting Minutes Department, Education Management Department, Practice Management Department, Security Management Department, Safety Management Department, Gas Cylinder Inventory Status Department, Gas Cylinder Incoming Diary, and Gas Cylinder Export Daily Department,
The equipment management module is,
Smart factory system including equipment import/export status department, equipment export management department, equipment import management department, equipment information management department, equipment repair management department, equipment calibration management ledger, and equipment usage log. In claim 1,
The test management module is,
Includes test application management department, test progress status department, test preparation register, test data management department, test result management department, report management department, and report revision request department,
The sample management module is,
Includes sample receipt management department, sample receipt/delivery management department, and sample inventory status department,
The system management module is,
Smart factory system including code management department, user setting department, user application management department, department management department, rank management department, corporate information management department, log management department, schedule management department, payment form department, and barcode management department. In claim 1,
The monitoring module is,
Includes report issuance status department, test progress status department, temperature and humidity status department, defect rate status department, test laboratory environment setting department, first equipment data status department, and second equipment data status department,
The production management module is,
Schedule Management Department, Progress Status Department, Quality Management Department, Performance Management Department, Purchasing and Inventory Management Department, Outsourcing Production Management Department, Arrival/Delivery Management Department, Product Delivery Status Department, Product Delivery Management Department, Product Arrival/Delivery Status Department, Product Inventory Status Department, Work Planning Department, Work Includes the instruction management department, work waiting status department, work log management department, and work defect management department,
The material management module is,
Smart factory system including material order management department, material inventory management department, material shipment management department, material arrival and shipment status department, material inventory status department, and material inventory management department. In claim 1,
The smart factory system further includes an intranet server,
The intranet server is,
Schedule module to register and manage monthly, weekly and daily schedules;
Work log module that registers and manages daily and weekly tasks;
Electronic payment module that sets the payment route and manages in-progress and completed payment documents;
Notice module where the administrator registers notices; and
A user management module that sets permissions for users to access the smart factory system;
Smart factory system including.

Images