Data management method and device, storage medium and program product
By splitting the basic data tables and creating custom business data models, multi-table linkage import and flexible data review process are realized, which solves the problems of low efficiency and high maintenance costs in the semiconductor manufacturing industry, and improves data import Efficiency and flexibility.
Patent Information
- Application Number
- CN202411046056.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-11-12
AI Technical Summary
The import or synchronization of basic data in the semiconductor manufacturing industry takes time, is inefficient, has high data maintenance costs, and the data import needs of different users and scenarios cannot be flexibly met.
By splitting the basic data tables, multiple data modules are generated, and users can create customized business data models, realize multi-table linkage import, provide data review process and flexible approval process configuration, adapt to different scenarios and users need.
It significantly reduces the time for data collection, sorting, aggregation and import, improves the efficiency of data import or synchronization, meets the needs of different scenarios and users, and reduces data maintenance costs.
Smart Images

Figure CN118939639A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and more specifically, to a data management method, device, storage medium, and program product. Background Art
[0002] The semiconductor manufacturing industry is a highly sophisticated industry with very strict requirements on basic data. On the one hand, the basic data is highly segmented, and on the other hand, different types of basic data are usually managed by different personnel. In related technologies, the basic data of the semiconductor manufacturing industry and the production data generated during the production process are managed and controlled through the Manufacturing Execution System (MES).
[0003] Basic data usually includes personnel, equipment, materials and other related data. Different basic data are stored in different business systems. MES obtains the basic data required by the system from other business systems. The acquisition process includes the collection, organization, aggregation and import of basic data. The acquisition of basic data is time-consuming and inefficient. In addition, for different scenarios and different users, the imported data needs to be specifically collected, organized and aggregated, which further reduces the efficiency of data import and increases data maintenance costs. Summary of the invention
[0004] The purpose of the present disclosure is to provide a data management method, device, storage medium and program product to solve the technical problems in the related art that the import or synchronization of basic data is time-consuming, inefficient and has high data maintenance costs.
[0005] In order to achieve the above objectives, the present invention adopts the following technical solutions:
[0006] A first aspect of the present disclosure provides a data management method, comprising:
[0007] In response to a first user operation, a business data model is generated, wherein the business data model includes at least one data module, and any of the data modules includes at least one field in a basic data table;
[0008] In response to the second user operation, data of fields corresponding to each data module in the business data model is obtained from the basic data table and imported into the target system.
[0009] Optionally, after the step of acquiring data of corresponding fields of each data module in the business data model from the basic data table and importing the data into the target system, the step further includes:
[0010] In response to a third user operation, performing a data review on the imported data imported into the target system, the imported data including data of corresponding fields of each data module;
[0011] When the data review is passed, the imported data is published in the target system.
[0012] Optionally, the steps of performing a data review on the imported data into the target system include:
[0013] Perform data integrity check on the imported data into the target system;
[0014] If the data integrity check passes, the imported data is controlled to enter the review process, and when the review process passes, the data review is determined to have passed;
[0015] If the data integrity check fails or the review process fails, the data review is deemed to have failed.
[0016] Optionally, the review process includes at least one review node, and the review process is determined to be passed when all review nodes are passed; before the step of performing data review on the imported data imported into the target system, the step also includes:
[0017] A custom interface is provided, and in response to a fourth user operation, a review process corresponding to the business data model is created on the custom interface, wherein the review process includes a reviewer list and a review order.
[0018] Optionally, before the step of generating a business data model in response to the first user operation, the step further includes:
[0019] Creating a data module according to a basic data table, wherein the data module includes at least one field in the basic data table;
[0020] A data module library is generated according to the created data modules, wherein the data module library stores a plurality of data modules and a corresponding relationship between the data modules and the basic data table.
[0021] Optionally, the step of generating a business data model in response to the first user operation includes:
[0022] Determining a data module in response to a first user operation in a first interface, where the data modules in the data module library are displayed on the first interface, and the first user operation is an operation of a user selecting a data module in the first interface;
[0023] The business data model is generated according to the determined data module.
[0024] Optionally, before the step of determining the data module in response to the first user operation in the first interface, the step further includes:
[0025] Obtaining user information, and determining user rights based on the user information;
[0026] The data modules within the scope of the user's authority are acquired from the data module library and the first interface is generated. The data modules within the scope of the user's authority are displayed on the first interface.
[0027] Optionally, after the step of generating a business data model in response to the first user operation, the step further includes:
[0028] freezing or deleting the business data model in response to a fifth user operation; and / or
[0029] The business data model is controlled to enter a model review process, and the business data model is published in the target system when the model review is passed.
[0030] Optionally, after the step of creating a data module according to the basic data table, the following steps are further included:
[0031] In response to a sixth user operation, at least one of freezing, deleting, upgrading or activating the data module is performed, the data module storing version information; and / or
[0032] The data module is controlled to enter the module review process, and the data module is released in the target system when the module review is passed.
[0033] Optionally, the data management method further includes:
[0034] A browser-server architecture mode and / or a client-server architecture mode is provided, and the first user operation and the second user operation are detected in the browser-server architecture mode and / or the client-server architecture mode.
[0035] Optionally, the target system is a manufacturing execution system, and the basic data table includes at least one of a personnel basic data table, a material basic data table, and an equipment basic data table.
[0036] A second aspect of the present disclosure provides a data management device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the data management method described above when executing the program.
[0037] A third aspect of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the data management method described above when the program is executed by a processor.
[0038] A fourth aspect of the present disclosure provides a computer program product, including a computer program, which implements the steps of the data management method described above when executed by a processor.
[0039] The beneficial effects of the present disclosure are as follows:
[0040] The data management method of the disclosed embodiment splits the basic data table into multiple data modules by splitting the basic data table, and supports users to create customized business data models based on the data modules of each basic data table. Since the various data modules included in the business data model may come from different basic data tables, multi-table linkage import can be achieved when the business data model is used to import or synchronize basic data. Compared with the traditional one-by-one import, the time for data collection, organization, aggregation, and import can be significantly reduced, and the efficiency of data import or synchronization can be improved. Moreover, by supporting users to create customized business data models, flexible configuration of imported data can be achieved to meet the needs of different scenarios and different users for imported data, thereby improving data import efficiency and reducing data maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] The specific implementation methods of the present disclosure are further described in detail below with reference to the accompanying drawings.
[0042] Figure 1 A flowchart of a data management method provided by an embodiment of the present disclosure;
[0043] Figure 2 A process for performing data review on imported data into a target system provided in an embodiment of the present disclosure;
[0044] Figure 3 A schematic diagram of a first interface when creating a business data model provided by an embodiment of the present disclosure;
[0045] Figure 4 A schematic diagram of creating a business data model by freely combining data modules provided in an embodiment of the present disclosure;
[0046] Figure 5 A schematic diagram of a browser-server architecture provided for an embodiment of the present disclosure;
[0047] Figure 6 A schematic diagram of a client-server architecture provided for an embodiment of the present disclosure;
[0048] Figure 7 A schematic diagram of the implementation principle of the user creation data module provided for the implementation of the present disclosure;
[0049] Figure 8 A schematic diagram of the implementation principle of the data review process provided for the implementation of the present disclosure. DETAILED DESCRIPTION
[0050] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings of the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.
[0051] Unless otherwise defined, the technical terms or scientific terms used in the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. Similarly, similar words such as "one", "one" or "the" do not indicate quantity restrictions, but indicate that there is at least one. Similar words such as "include" or "comprise" mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Similar words such as "connect" or "connected" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0052] In order to better understand the technical solutions of the data management method, device, storage medium and program product disclosed in the present invention, the design concept of the present invention is first briefly introduced.
[0053] As a software system for managing and controlling manufacturing processes, MES plays a coordination and monitoring role in the production environment, helping manufacturing companies to collect, analyze and exchange production data in real time to optimize production efficiency, quality and resource utilization. MES assists production personnel in monitoring and managing the resources of the product manufacturing process in a digital and information-based manner. The resources include but are not limited to basic resources such as personnel, equipment, and materials. In specific implementation, MES monitors and manages the data corresponding to each resource to achieve monitoring and management of each resource. The data corresponding to each resource is described as follows:
[0054] 1. Personnel
[0055] Basic personnel data refers to employee information related to the production process, including key information such as employee number, name, position, skills, etc. This basic data is used to manage job allocation, time records, training needs, etc. Basic personnel data defines the identity and role of each employee in the organization, as well as the skills and qualification requirements associated with them.
[0056] 2. Equipment
[0057] The basic data of equipment refers to the information of various equipment and tools used for production, including key data such as equipment model, specification, status and location. These basic data are used for equipment scheduling, maintenance management, troubleshooting and other aspects. The basic data of equipment defines the important attributes of each equipment, such as model, specification, capacity, etc. It can also include information such as the production rate, maintenance cycle and calibration requirements of the equipment.
[0058] 3. Materials
[0059] The basic data of materials refers to the information of raw materials and finished products used for production, including key data such as material description, specifications, units and suppliers. These basic data are used in material procurement, inventory management, quality control, etc. The basic data of materials defines the attributes of each material, such as description, specifications, units and quality requirements.
[0060] The above basic data of personnel, equipment, materials, etc. are usually stored in different business systems, such as personnel management system, equipment management system, material management system, etc. MES needs to be integrated and share data with different business systems, and then MES can import relevant basic data from various business systems.
[0061] In the related art, when MES obtains basic data from other business systems, the acquisition process includes operations such as the collection, organization, aggregation and import of basic data. On the one hand, since the basic data required by MES is usually stored in multiple business systems, and the same basic data may be configured and managed by different business personnel, it is necessary to collect, aggregate and import data for each business system when obtaining basic data, resulting in a long data acquisition process, low efficiency, and easy to have problems such as incomplete data collection; on the other hand, for different users and different application scenarios, MES needs to import different basic data. The traditional data import method requires each user to perform personalized data collection, organization, aggregation and import operations from each business system for different application scenarios. It is impossible to flexibly and efficiently meet personalized data import needs. Data collection and organization takes a long time, which increases data maintenance costs.
[0062] In order to solve the above technical problems, the embodiments of the present disclosure provide a data management method, device, storage medium and program product. The specific embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.
[0063] Please refer to Figure 1 , Figure 1The flowchart of the data management method provided in the embodiment of the present disclosure is applied to a system that needs to import a large amount of basic data, such as a manufacturing execution system. Correspondingly, the business system storing the basic data generally includes various types of business systems such as a personnel management system, an equipment management system, and a material management system. The basic data tables corresponding to each business system can be respectively represented as a personnel basic data table, an equipment basic data table, and a material basic data table. The present disclosure is described by taking the import of a manufacturing execution system from a personnel management system, an equipment management system, a material management system and other systems as an example. It can be understood that the data management method of the present disclosure can also be applied to data import or synchronization solutions of other systems.
[0064] like Figure 1 As shown, the data management method includes the following steps:
[0065] Step S101, generating a business data model in response to a first user operation, wherein the business data model includes at least one data module, and any of the data modules includes at least one field in a basic data table. Exemplarily, the first user operation is an operation of a user triggering the creation of a business data model.
[0066] Step S102, in response to the second user operation, obtain the data of the corresponding fields of each data module in the business data model from the basic data table and import it into the target system. Exemplarily, the second user operation is an operation of the user triggering the import of data, such as the user selecting any business data model and using the business data model to import or synchronize data.
[0067] Compared with the related art, the data management method of the embodiment of the present invention splits the basic data table into multiple data modules by splitting the basic data table, and supports users to create customized business data models based on the data modules of each basic data table. Since the various data modules included in the business data model may come from different basic data tables, multi-table linkage import can be achieved when the business data model is used to import or synchronize basic data. Compared with the traditional one-by-one import, the time for data collection, collation, aggregation, and import can be significantly reduced, and the efficiency of data import or synchronization can be improved; and by supporting users to create customized business data models, flexible configuration of imported data can be achieved to meet the needs of different scenarios and different users for imported data, thereby improving data import efficiency and reducing data maintenance costs.
[0068] In the disclosed embodiment, each basic data table corresponds to a business system, and the basic data table is a data table stored in the background server of the business system. Exemplarily, the basic data table includes at least one of a personnel basic data table, a material basic data table, and an equipment basic data table. Among them, for any basic data table, it includes multiple fields and basic data under each field. In order to facilitate the flexible construction of a business data model, the disclosed embodiment first splits each basic data table, and splits each basic data table into multiple data modules, wherein each data module includes at least one field in the corresponding basic data table.
[0069] In one possible implementation, before the step of generating a business data model in response to a first user operation, the step also includes: (1) creating a data module based on a basic data table, wherein the data module includes at least one field in the basic data table; and (2) generating a data module library based on the created data module, wherein the data module library stores a plurality of data modules and the correspondence between the data modules and the basic data table.
[0070] For example, the basic personnel data table includes the following information: (1) Employee information: records the basic information of each employee, such as name, work number, position, department, etc. (2) Skills and qualifications: records the skills and qualifications of employees, such as training records, certification certificates, etc. This data helps to match and reasonably arrange job assignments and employee scheduling. (3) Work experience: records the work experience of employees, including previous jobs, relevant project experience, etc. This data helps to better understand the background and potential of employees. (4) Training needs: records the current and future training needs of employees in order to make training plans and resource allocation.
[0071] Exemplarily, the equipment basic data table includes the following information: (1) Equipment attributes: record the key attributes of each equipment, such as model, specifications, production rate, capacity, etc. These attributes help to classify, identify and distinguish equipment. (2) Status and operating parameters: record the status information of the equipment, such as operation, failure, maintenance, etc. At the same time, the operating parameters of the equipment can also be recorded, such as temperature, pressure, speed, etc. (3) Maintenance plan: record the maintenance plan and maintenance history of the equipment, including maintenance records, maintenance plans and calibration requirements, etc. This helps to ensure the normal operation and reliability of the equipment. (4) Safety specifications: record the safety specifications and operating guidelines of the equipment to ensure that employees comply with relevant safety standards and procedures when using the equipment.
[0072] For example, the material basic data table includes the following information: (1) Material description and coding: Describe each material and assign it a unique identification code, such as material name, model, batch, etc. This helps to accurately track and identify materials during the production process. (2) Specifications and characteristics: Record the material's specifications, technical parameters, and quality standards. This helps ensure that the material meets the expected quality requirements during the production process. (3) Supplier information: Record the supplier information related to the material, such as supplier name, contact information, delivery conditions, etc., which helps with material procurement and supply chain management.
[0073] It can be seen that the basic data tables include multiple types of information, and each type of information can be represented by one or more fields. For example, employee information in the personnel basic data table can be represented by fields such as name, work number, position, department, etc., and skill information can be represented by fields such as training records and certification certificates.
[0074] In specific implementation, developers can split each basic data table into multiple data modules according to actual business needs and the specific information of each basic data table, such as splitting the basic personnel data table into basic personnel information data module, personnel title information data module, personnel skill technology data module, etc. After the data module is created, each data module needs to be saved to the system through the modeling tool. Each data module constitutes a data module library. Subsequent users can directly use each data module in the data module library to create a business data model that meets personalized needs, and each data module can be reused.
[0075] It is understandable that before creating a data module, it is necessary to pre-configure the names of each basic data table and the fields contained in each basic data table in the system. Based on this configuration information, users can create customized data modules according to actual business needs.
[0076] In a possible implementation, the data management method of the present invention can support other operations besides creating data modules, such as freezing, deleting, modifying, upgrading or activating data modules. Exemplarily, the data management method of the present invention also includes the following steps:
[0077] (1) in response to a sixth user operation, at least one of freezing, deleting, upgrading or activating the data module is performed, the data module storing version information; and / or
[0078] (2) Controlling the data module to enter the module review process, and publishing the data module in the target system when the module review is passed.
[0079] Optionally, after a data module is created, the data module can be solidified by freezing operation. In the frozen state, the data module cannot be edited or deleted again, so that the confirmed data module can be prevented from being tampered with. For a data module in a frozen state, it can also be activated by activation operation and released to the target system after activation. Among them, the sixth user operation is an operation triggered by the user to freeze, delete, upgrade or activate the data module.
[0080] In order to ensure the accuracy and applicability of the data module, a sign-off mechanism (or module review process) can be introduced during the activation process to determine whether the data module is accurate and applicable. The module review process will generate detailed approval records, including the approver, approval time, approval results and other information. The approval record is helpful for subsequent problem tracking. Only when the module is approved, the data module is allowed to be published in the target system.
[0081] In addition, when it is necessary to modify the published data module, the system supports upgrading the data module. Specifically, the data module stored in the data module library of the present disclosure will set a version information bit to identify the version information of the data module, such as the initial version information is 1.0. When the user modifies the data module, the version information bit of the modified data module can be expressed as 2.0. By distinguishing different versions of the data module by the version number, the change history and status of each version can be clearly tracked. At the same time, version control also supports rollback operations, that is, it can be restored to a previous stable version when necessary. Exemplary, assuming that a data module A includes two fields, product and price, and its corresponding version information is 1.0. Later, according to business needs, it is necessary to import the supplier information of the product. At this time, the data module A can be upgraded, and the data module A is modified to include three fields of product, price, and supplier, and the version information is set to 2.0. When the subsequent user uses the data module A to build a business data model, the appropriate version of the data module A can be selected according to actual needs.
[0082] In a possible implementation, after the step of obtaining the data of the fields corresponding to each data module in the business data model from the basic data table and importing it into the target system, it also includes: performing a data review on the imported data imported into the target system in response to a third user operation, the imported data including the data of the fields corresponding to each data module; and publishing the imported data in the target system when the data review passes.
[0083] Specifically, after data is imported into the target system through the business data model, the imported data is usually temporarily stored. At this time, the imported data needs to be reviewed. Only when the data review is passed, the imported data will be saved in the target system (such as transferred from the temporary storage area to the production database or data warehouse) and released. The release of imported data is equivalent to activating the imported data in the target system. After activation, the data is accessible and used by other systems or users. Exemplarily, after the user imports the data, he can click the data review button (i.e., the third user operation) to control the data review process of the imported data.
[0084] Optional, please refer to Figure 2 , Figure 2 The process of performing data review on the imported data into the target system provided by the embodiment of the present disclosure is as follows: Figure 2 As shown, the following steps are included:
[0085] Step S201, perform data integrity check on the imported data into the target system, if the data integrity check passes, execute step S202, if the data integrity check fails, execute step S203.
[0086] During data review, the data integrity check is first performed, including checking whether the data is complete, the format is correct, whether it contains necessary fields, etc. For example, a comprehensive check of the imported data is performed through preset verification rules (such as field non-empty verification, data format verification, etc.). If the data integrity check passes, it means that the data is complete at the basic level and can enter the next step of the review process.
[0087] Step S202, control the imported data to enter the review process, when the review process passes, execute step S203, if the review process fails, execute step S204.
[0088] Step S203: determine if the data review has passed, import the data and activate it online.
[0089] Step S204: determine that the data review fails and the imported data is rejected.
[0090] In the disclosed embodiment, the dual protection of data integrity verification and review process effectively improves the quality of imported data and avoids system problems or business risks caused by data errors.
[0091] In a possible implementation, the review process includes at least one review node. The review process is considered to be passed when all review nodes are passed. For any review node, if it fails, it returns to the previous review node. If it passes, it enters the next review node.
[0092] For example, after the reviewer logs into the system, he can view the imported data to be reviewed and perform review operations (such as approval, rejection, modification suggestions, etc.). The review results will be fed back to the system in real time, and will continue to be pushed to the next reviewer according to the review process, or the data will be activated and put online. In the specific implementation, a web interface or mobile application interface is provided to the reviewer to display the list of pending review and the review details. The review operation is submitted to the back-end service through the API interface. The back-end service updates the review status according to the review results and triggers subsequent processes. In addition, when the review process is triggered, the system will automatically push the imported data to the first reviewer, and notify the reviewer to review through email, SMS or system messages. The automated push and notification mechanism significantly improves the review efficiency, reduces manual intervention and waiting time, and makes the review process more efficient and quick.
[0093] Optionally, before the step of conducting data review on the imported data imported into the target system, it also includes: providing a custom interface, creating a review process corresponding to the business data model on the custom interface in response to a fourth user operation, the review process including a reviewer list and a review order. The data management method of the disclosed embodiment supports flexible review process configuration, allowing administrators or system administrators to customize review nodes, reviewers and review order according to business needs. In specific implementation, a workflow engine (such as Activiti, Camunda, etc.) or a custom process management module can be used to realize the dynamic configuration of the review process. For example, through a graphical interface (such as the above-mentioned custom interface), users can intuitively set the review process and save it as a configuration file or database record (the operation involved in the user creating the review process on the custom interface is the above-mentioned fourth user operation). Through flexible review process configuration, the problem of inconsistent review processes for different customers can be solved, so that the system can adapt to diverse business needs.
[0094] In one possible implementation, the step of generating a business data model in response to a first user operation includes: determining a data module in response to a first user operation in a first interface, the first interface displaying data modules in the data module library, the first user operation being an operation of a user selecting a data module in the first interface; and generating the business data model based on the determined data module.
[0095] For example, please refer to Figure 3 , Figure 3 is a schematic diagram of the first interface of the embodiment of the present disclosure, such as Figure 3As shown, multiple data modules are displayed on the first interface. Users can select and configure the required data modules through the first interface, allowing users to quickly build customized business data models by selecting, dragging and dropping data modules. At the same time, the data management method of the present invention also supports functions such as freezing, saving, exporting, and importing business data models. By providing a visual configuration tool, users are allowed to adjust the business data model according to actual needs. This flexibility ensures that the system can adapt to changing business needs. Exemplary, Figure 3 The left area in the middle shows the name list of the business data models in the target system. The gray fill of data module 1 in the middle area indicates the currently selected data module 1. Field 1, Field 2, Field 3, and Field 4 on the right side of the middle area indicate the fields contained in data module 1. The Create, Remove, and Modify buttons in the right area indicate creating, deleting, and modifying business data models, respectively.
[0096] For example, please refer to Figure 4 , Figure 4 A schematic diagram of creating a business data model according to a free combination of data modules provided in an embodiment of the present disclosure, such as Figure 4 As shown, assuming that the data module library includes 5 data modules, represented as data module 1, data module 2, data module 3, data module 4, and data module 5 respectively, the user can customize the business data model according to the actual business needs based on the data module library, such as creating a business data model 1 including data module 1, data module 3, and data module 4; or creating a business data model 2 including data module 1, data module 2, and data module 5; or creating a business data model 3 including data module 4 and data module 5.
[0097] In one possible implementation, before the step of determining the data module in response to the first user operation in the first interface, the step also includes: (1) obtaining user information and determining user authority based on the user information; (2) obtaining data modules within the user authority range from the data module library and generating the first interface, on which the data modules within the user authority range are displayed.
[0098] In this embodiment, when the user creates a business data model, user authority management is also set up to ensure data security and access compliance. Specifically, when a user creates or modifies a business data model, the system first obtains user information, which includes but is not limited to user name, user role, department, etc. Then, based on the user information, the system determines the data module within the user's authority by querying the authority database or applying preset authority rules. By integrating user authority management into the creation process of the business data model, data security can be effectively protected to prevent unauthorized access and sensitive data leakage. This implementation method not only improves the security of the system, but also improves the user experience, allowing users to more conveniently perform business operations according to their own authority.
[0099] In a possible implementation, after the step of generating a business data model in response to the first user operation, the method further includes: freezing or deleting the business data model in response to a fifth user operation; and / or controlling the business data model to enter a model review process, and publishing the business data model in the target system when the model review passes. The fifth user operation is an operation of freezing or deleting the business data model by the user.
[0100] Specifically, after a business data model is created, it can be solidified through the freezing operation. In the frozen state, the business data model cannot be edited or deleted again, so as to prevent the confirmed business data model from being tampered with. For a frozen business data model, it can also be activated through the activation operation, and then published to the target system. After that, all basic data in the target system can be imported or synchronized using the business data model, which greatly reduces the time for customers to collect and organize data.
[0101] Furthermore, in order to ensure the accuracy and applicability of the business data model, a sign-off mechanism (or model review process) can be introduced during the activation process to determine whether the business data model is accurate and applicable through model review. The model review process will generate detailed approval records, including information such as the approver, approval time, and approval results. The approval record will help track issues later. Only when the model is approved can the business data model be published in the target system. It should be noted that the business data model can also support modification operations, and the modified business data model can also be saved as an upgraded version.
[0102] Exemplarily, the model review process includes at least one review node. The model review is considered to be passed when all review nodes are passed. For any review node, if it fails, it returns to the previous review node. If it passes, it proceeds to the next review node.
[0103] In a possible implementation, the data management method disclosed herein further includes the following steps: storing the data module, business data model, data review process, module review process, model review process, imported data and other information in an Oracle database. As the data storage center of the system, the Oracle database is responsible for persisting all data, including data modules created by users, business data models, and basic data actually imported.
[0104] In one possible implementation, a system using the data management method of the present invention supports a browser-server architecture mode and a client-server architecture mode, and the data management method of the present invention also includes the following contents: providing a browser-server architecture mode and / or a client-server architecture mode, and detecting user operations under the browser-server architecture mode and / or the client-server architecture mode, and the user operations include but are not limited to the above-mentioned first user operation and the second user operation.
[0105] Please refer to Figure 5 , Figure 5 This is a schematic diagram of the browser-server architecture (Browser / Server, referred to as B / S), such as Figure 5 As shown in the figure, B / S architecture is a network architecture model that concentrates the core part of system function implementation on the server, while simplifying the development, maintenance and use of the system. Users can access applications on the server through a browser without installing other client software locally. It usually has a three-layer structure:
[0106] (1) Presentation layer: Users access the system through a Web browser. The browser is responsible for displaying the user interface and receiving user input. The interaction between the presentation layer and the user is intuitive and does not require the installation of additional client software.
[0107] (2) Application layer: This layer is located on the server side and is the core part of the system. It is responsible for processing all business rules and data validation, receiving requests from the presentation layer, and returning processing results to the presentation layer. The application layer is a bridge connecting the presentation layer and the operation layer, ensuring the accuracy of data and the correctness of business processes.
[0108] (3) Operation layer: Responsible for interacting with the database (such as Oracle19c) and performing operations such as adding, deleting, modifying and querying data. The operation layer encapsulates all database-related operation details and provides a unified data access interface for the application layer.
[0109] In the browser-server architecture mode, users send HTTP requests to the server through the browser, and the server returns an HTTP response after processing the request. The response may contain HTML pages, JSON data, or other formats of data to update the user interface on the browser.
[0110] Please refer to Figure 6 , Figure 6 A schematic diagram of a client-server architecture is shown in Figure 6 As shown in Figure 1, the client-server architecture (Client / Server, referred to as C / S) divides the software application into two main parts: the client and the server, which communicate and exchange data through the network. It usually adopts a two-layer structure:
[0111] (1) Client: The client is the interface for direct user interaction. It is responsible for receiving user input, displaying processing results, and sending requests to the server. It usually runs on the user's own computer and has a graphical user interface (GUI) to display data returned by the server and allow users to input and operate.
[0112] (2) Server: The server is responsible for data management and business logic processing. The client is developed using C# language and winform framework, and the server is developed using Java language and sping boot framework. The data exchange between the client and server uses XML format, and RabbitMQ is used for message publishing and subscription processing, and Oracle 19c is selected as the database. The C / S architecture has the advantages of fast response speed, high security, and easy management. By using modern technology stacks (such as C#, Java, Spring Boot, RabbitMQ, Oracle, etc.), the maintainability, scalability and high performance of the system can be ensured.
[0113] In specific applications, the data management method of the disclosed embodiment is mainly used in two aspects: the first aspect can be understood as the development stage, in which developers or users can maintain data modules, business data models, data review processes, module review processes, and model review processes, including creation, modification, editing, search and other operations, at which time the browser-server architecture can be used first; the second part can be represented as the factory user use stage, in which users can select business data models for data import, data review and other operations, at which time the client-server architecture can be used. Providing two architecture modes helps to expand the scope of application and flexibility of the system and enhance the scalability and maintainability of the system.
[0114] For example, the implementation process of a user creating a data module is as follows: Figure 7 As shown, including the following:
[0115] (1)User login—>Menu Loading (get User Menu)—>Into menu (Import template Setting)—>Http request json to load the menu.
[0116] This part corresponds to the process in which the user logs in on the browser interface and the browser sends an Http request.
[0117] (2)User Operation—>Modeling—>Create—>Http request json.
[0118] This part corresponds to the user operation. The user enters the modeling interface, clicks "Create", and the browser sends an HTTP request to the server.
[0119] (3)User key Information—>System Loading data—>System call getCommonQuery().
[0120] This part corresponds to the process of the system obtaining user information and loading data that matches the user's permissions.
[0121] (4) User Commit—> System call get CommonSavedate()—> Server ReturnSuccess—> DB persists data.
[0122] This part corresponds to the process of the user creating a data module and the server saving data (ie, saving the newly created data module).
[0123] (5) The front end renders the data module interface.
[0124] It is understandable that the implementation process of a user creating a business data model is the same as the implementation process of creating a data module, and will not be repeated here.
[0125] For example, the data review process is as follows: Figure 8 As shown, including the following:
[0126] (1)User login—>Menu Loading (get User Menu)—>Into menu (InformationImport)—>Http request json to load the menu.
[0127] This part corresponds to the user's login process.
[0128] (2)User Operation—>Modeling—>Choose Import—>Http request json.
[0129] This part corresponds to user operations. The user enters the model interface, selects import, and sends an Http request.
[0130] (3)User Operation—>Choose Aduit—>System call get DataCheckUser()—>Server Return check Node.
[0131] This part corresponds to the process in which the user operates, selects the reviewer, and the server obtains the reviewer information and returns the review node.
[0132] (4) User Audit—>System calls getDateCheckInformation()—>Server CheckSuccess—>Server executes changeCheck State()—>Server executes active ImportData()—>DB persists data.
[0133] This part corresponds to the process of review, review status change, imported data activation, and imported data persistence under the review node.
[0134] (5) The front end renders the data module interface—>Into check Node page.
[0135] This part corresponds to the process of entering the review node.
[0136] Based on the same inventive concept, the second aspect of the present disclosure provides a data management device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the data management method described above when executing the program.
[0137] Based on the same inventive concept, a third aspect of the present disclosure provides a manufacturing execution system, comprising the data management device as described above.
[0138] Exemplarily, the manufacturing execution system is applied to the semiconductor manufacturing industry, such as in a semiconductor packaging and testing factory. The manufacturing execution system of the disclosed embodiment is conducive to improving the collection, organization, and integration of basic data in the semiconductor packaging and testing factory, and improving the efficiency of importing or synchronizing basic data.
[0139] Based on the same inventive concept, the fourth aspect of the present disclosure provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of the data management method described above are implemented.
[0140] In the specific implementation process, the computer storage medium may include: Universal Serial Bus Flash Drive (USB), mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other storage media that can store program codes.
[0141] Based on the same inventive concept, the fifth aspect of the present disclosure provides a computer program product, including a computer program, which implements the steps of the data management method described above when executed by a processor. Since the principle of solving the problem by the above computer program is similar to the principle of the data management method, the implementation of the above computer program can refer to the implementation of the data management method, and the repeated parts will not be repeated.
[0142] The computer program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more conductors, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.
[0143] Obviously, the above embodiments of the present disclosure are merely examples for clearly illustrating the present disclosure, and are not limitations on the implementation methods of the present disclosure. For ordinary technicians in this field, other different forms of changes or modifications can be made on the basis of the above description. It is impossible to list all the implementation methods here. All obvious changes or modifications derived from the technical solution of the present disclosure are still within the protection scope of the present disclosure.
Claims
1. A data management method, It is characterized in that The following steps are involved: In response to a first user operation, a business data model is generated, wherein the business data model includes at least one data module, and any of the data modules includes at least one field in a basic data table; In response to the second user operation, data of fields corresponding to each data module in the business data model is obtained from the basic data table and imported into the target system.
2. The data management method according to claim 1, It is characterized in that After the step of acquiring data corresponding to fields of each data module in the business data model from the basic data table and importing the data into the target system, the following step further includes: In response to a third user operation, performing a data review on the imported data imported into the target system, the imported data including data of corresponding fields of each data module; When the data review is passed, the imported data is published in the target system.
3. The data management method according to claim 2, It is characterized in that The steps for data review of the imported data into the target system include: Perform data integrity check on the imported data into the target system; If the data integrity check passes, the imported data is controlled to enter the review process, and when the review process passes, the data review is determined to have passed; If the data integrity check fails or the review process fails, the data review is deemed to have failed.
4. The data management method according to claim 3, It is characterized in that The review process includes at least one review node, and the review process is determined to be passed when all review nodes are passed; The step of data review for the imported data into the target system also includes: A custom interface is provided, and in response to a fourth user operation, a review process corresponding to the business data model is created on the custom interface, wherein the review process includes a reviewer list and a review order.
5. The data management method according to claim 1, It is characterized in that Before the step of generating a business data model in response to the first user operation, the method further includes: Creating a data module according to a basic data table, wherein the data module includes at least one field in the basic data table; A data module library is generated according to the created data modules, wherein the data module library stores a plurality of data modules and a corresponding relationship between the data modules and the basic data table.
6. The data management method according to claim 5, It is characterized in that The step of generating a business data model in response to a first user operation includes: Determining a data module in response to a first user operation in a first interface, where the data modules in the data module library are displayed on the first interface, and the first user operation is an operation of a user selecting a data module in the first interface; The business data model is generated according to the determined data module.
7. The data management method according to claim 6, It is characterized in that Before the step of determining the data module in response to the first user operation in the first interface, the method further includes: Obtaining user information, and determining user rights based on the user information; The data modules within the scope of the user's authority are acquired from the data module library and the first interface is generated. The data modules within the scope of the user's authority are displayed on the first interface.
8. The data management method according to claim 1, It is characterized in that After the step of generating a business data model in response to the first user operation, the method further includes: freezing or deleting the business data model in response to a fifth user operation; and / or The business data model is controlled to enter a model review process, and the business data model is published in the target system when the model review is passed.
9. The data management method according to claim 5, It is characterized in that The steps of creating a data module based on the basic data table also include: In response to a sixth user operation, at least one of freezing, deleting, upgrading or activating the data module is performed, the data module storing version information; and / or The data module is controlled to enter the module review process, and the data module is released in the target system when the module review is passed.
10. The data management method according to claim 1, It is characterized in that The data management method further comprises: A browser-server architecture mode and / or a client-server architecture mode is provided, and the first user operation and the second user operation are detected in the browser-server architecture mode and / or the client-server architecture mode.
11. The data management method according to claim 1, It is characterized in that The target system is a manufacturing execution system, and the basic data table includes at least one of a personnel basic data table, a material basic data table, and an equipment basic data table.
12. A data management device, It is characterized in that The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the data management method according to any one of claims 1 to 11 are implemented.
13. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the program is executed by a processor, the steps of the data management method according to any one of claims 1 to 11 are implemented.
14. A computer program product comprising a computer program, It is characterized in that When the computer program is executed by a processor, the steps of the data management method according to any one of claims 1 to 11 are implemented.
Citation Information
Patent Citations
Data migration method and device based on data model
CN111581183A
Master data full life cycle management method and system, engine and storage medium
CN114707953A
Data synchronization method and device, electronic equipment and storage medium
CN116756244A
Machine automatic examination and approval method based on GLM big data model engine analysis decision
CN117333139A
