Electronic part information management method and system and storage medium

Abstract

The invention relates to the field of digital management, and discloses an electronic part information management method and system and a storage medium. The electronic part information management system comprises a data interface unit used for capturing and inputting electronic part information; the data extraction unit is used for acquiring an electronic part identifier; the data cleaning unit is used for processing invalid information in the intermediate data file; the data normalizing unit is used for performing standardization and consistency check; the data conversion unit is used for outputting an electronic part information form; and the data exploration unit is used for carrying out scheme design, part optimization and purchase cost analysis. According to the electronic part information management system provided by the invention, the work efficiency of BOM, ECN and ERP manufacturing methods and management is improved through automatic processing, the data accuracy and information visualization are improved, the scheme design of an electronic part optimization type is facilitated, a design additional value is generated, and meanwhile, the labor cost and the time cost of purchase decision making are also saved.

Description

Technical Field

[0001] The present invention relates to the field of digital management, and in particular to an electronic parts information management method, system and storage medium. Background Art

[0002] Nowadays, many manufacturing fields will produce BOM (Bill of Material) and ECN (Engineering Change Notice) files, and use ERP (Enterprise Resource Planning) system for manufacturing management. BOM is a file that describes the product structure in a data format and is a product structure data file that can be recognized by computers. The ERP system is a comprehensive information system centered on the enterprise. It integrates various business modules within the enterprise, including procurement, sales, warehouse management, production planning, financial management, etc.

[0003] The traditional method of making BOM and ECN files is to first use EDA (Electronic Design Automation) tools to generate an electronic parts list after the circuit diagram and structural drawings are designed, and then manually enter and compare with the company's own parts library to complete the production of BOM and ECN files. In addition, designers need to refer to the ERP material list and enter the ERP number into the parts list before entering the ERP system for procurement. In order to meet the needs of specific industry production, manufacturing, procurement and other usage scenarios, it is necessary to summarize and enter the name, specification, quantity, manufacturer, ERP number, price and other information of the parts in the EDA tool or EXCEL table for manufacturing implementation. Because the software data interface is not unified, especially the wide variety of electronic parts, the above method is not only time-consuming and labor-intensive, but also often results in information omissions and data format errors.

[0004] There are many types of electronic parts. The traditional BOM, ECN file production and ERP number input methods are inefficient, the accuracy of manual production is poor, the data interfaces of various software are not unified, the visualization of electronic parts information, data interaction and data analysis are poor, which is not conducive to solution design and electronic parts optimization, nor is it conducive to procurement decisions to save manpower and time costs. Summary of the invention

[0005] The purpose of the present invention is to overcome the shortcomings of the prior art in producing BOM and ECN files, such as low efficiency, poor accuracy of manual production, non-uniform data interfaces of various software, poor visualization of electronic parts information and data interaction and data analysis, which are not conducive to scheme design and electronic parts optimization, and are not conducive to procurement decisions to save manpower and time costs. An electronic parts information management method, system and storage medium are provided.

[0006] In order to achieve the above-mentioned object of the invention, the present invention provides the following technical solutions:

[0007] The present invention provides an electronic parts information management system, comprising: a data interface unit, used for capturing and inputting electronic parts information; a data extraction unit, used for obtaining electronic parts identification and generating an intermediate data file; a data cleaning unit, used for processing invalid information in the intermediate data file; a data regularization unit, used for normalizing and consistency checking the intermediate data file after data cleaning; a data conversion unit, used for outputting an electronic parts information form; wherein the electronic parts information form includes at least one of engineering BOM, ERP BOM, and ECN; and a data exploration unit, used for performing scheme design, parts optimization, and procurement cost analysis on the electronic parts information form.

[0008] According to a preferred embodiment, the data interface unit uses an application program interface. The data interface unit at least calls one of voice, text, image, web page, and EDA tool interface to capture and input electronic component information and generate a copy of the original interface data file.

[0009] According to a preferred embodiment, the data extraction unit converts the original interface data file copy into an intermediate data file of a unified format. The format of the original interface data file includes at least one of MP3, AAC, XLS, TXT, RTF, DOC, PDF, HTML, and PPT. The data extraction unit can identify the part identification carried in the corresponding format data.

[0010] According to a preferred implementation, the data regularization unit performs data normalization and consistency check on the intermediate data file after data cleaning by matching the electronic parts coding rules and query rules of the local predefined database to generate a final data file.

[0011] According to a preferred embodiment, the data conversion unit converts the final data file into an electronic component information form in a corresponding format and outputs it.

[0012] The present invention also provides a method for using an electronic parts information management system, which uses the electronic parts information management system provided by the present invention to convert the original design BOM data in the original format created by EDA software into an engineering BOM.

[0013] The present invention also provides a method for using an electronic parts information management system, and uses the electronic parts information management system provided by the present invention to convert the engineering BOM into an ERP BOM.

[0014] The present invention also provides a method for using an electronic parts information management system, and uses the electronic parts information management system provided by the present invention to generate ECN.

[0015] The present invention also provides an electronic parts information management method, which is implemented using the electronic parts information management system provided by the present invention. The electronic parts information management method includes the following steps:

[0016] S001: Data interface unit initialization;

[0017] S002: Electronic parts information extraction;

[0018] S003: Clean the data;

[0019] S004: Regularize the data;

[0020] S005: transform the data;

[0021] S006: Conduct data exploration;

[0022] S007: Information visualization and notification.

[0023] The present invention also provides a storage medium on which a readable computer program is stored. When the computer program is executed by a processor, the processor runs the electronic parts information management system provided by the present invention.

[0024] Compared with the prior art, the present invention has the following beneficial effects:

[0025] The electronic parts information management system provided by the present invention improves the work efficiency of BOM, ECN and ERP production methods and management, improves data accuracy and information visualization through automated processing, is conducive to the optimization of electronic parts design and generation of design added value, and also saves the manpower and time costs of procurement decisions. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 A schematic diagram of a functional radiation block diagram of an electronic parts information management system provided by the present invention;

[0027] Figure 2 A schematic diagram of data format conversion when acquiring raw data for an electronic parts information management system provided by the present invention;

[0028] Figure 3 A schematic block diagram of an algorithm for an electronic parts information management system provided by the present invention;

[0029] Figure 4 Map and reconstruct flow charts for original design BOM, engineering BOM, and ERP BOM;

[0030] Figure 5 A schematic diagram of a process for generating a project BOM using the electronic parts information management system provided by the present invention;

[0031] Figure 6 A schematic diagram of the process of generating ERP BOM for the electronic parts information management system provided by the present invention;

[0032] Figure 7 A schematic diagram of the process of generating ECN for the electronic parts information management system provided by the present invention;

[0033] Figure 8 A schematic diagram of an electronic parts information management method provided by the present invention. DETAILED DESCRIPTION

[0034] The present invention is further described in detail below in conjunction with test examples and specific implementation methods. However, this should not be understood as the scope of the above subject matter of the present invention being limited to the following embodiments, and all technologies realized based on the content of the present invention belong to the scope of the present invention.

[0035] Unless otherwise specified, in the description of the specific embodiments of the present invention, the terms indicating the orientation or position relationship such as "up", "down", "left", "right", "center", "inside", "outside", etc. are all expressions based on the orientation or position relationship shown in the drawings, or the orientation or position relationship when the invented product / equipment / device is usually used. These terms of orientation or position relationship are only for the convenience of describing the scheme of the present invention or simplifying the description in the specific embodiments, so as to facilitate the technicians to quickly understand the scheme, rather than indicating or implying that a specific device / component / element must have a specific orientation, or be constructed and operated in a specific position relationship, and therefore cannot be understood as a limitation on the present invention.

[0036] In addition, if the terms "horizontal", "vertical", "overhanging", "parallel" and the like appear, it does not mean that the corresponding devices / components / elements are required to be absolutely horizontal or vertical or overhanging or parallel, but may be slightly tilted or have deviations. For example, "horizontal" only means that its direction is more horizontal than "vertical", and does not mean that the structure must be completely horizontal, but may be slightly tilted. Alternatively, it can be simplified to mean that the corresponding devices / components / elements are set in directions such as "horizontal", "vertical", "overhanging", "parallel", etc., and can have an error / deviation of ±10% relative to the corresponding direction setting, more preferably an error / deviation within ±8%, more preferably an error / deviation within ±6%, more preferably an error / deviation within ±5%, and more preferably an error / deviation within ±4%. As long as the corresponding device / component / element is within the error / deviation range, it can still achieve its role in the scheme of the present invention.

[0037] In addition, the expressions “first”, “second”, “third”, etc. that appear in the terms are merely descriptions used to distinguish the same or similar components and should not be understood as emphasizing or implying the relative importance of specific components.

[0038] In addition, in the description of the embodiments of the present invention, "several", "plurality" and "a number" represent at least 2. It can be any number such as 2, 3, 4, 5, 6, 7, 8, 9, and even more than 9.

[0039] In addition, in the description of the technical solution of the present invention, unless otherwise clearly specified / defined / restricted, the terms "set", "install", "connect", "connected", "provided with", "laid", and "arranged" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection, and can be welding, riveting, bolting, threading, and other commonly used connection means in the field. This connection can be a mechanical connection, an electrical connection, or a communication connection; it can be a direct connection, or an indirect connection through an intermediate medium, and it can be the internal connection of two elements.

[0040] Example 1

[0041] This embodiment provides an electronic parts information management system. Figure 1 The functions of the electronic parts information management system include part status query, operation authority setting, part and file information change, comparative analysis, document association, milestones, notifications, etc. The electronic parts information management system can also realize authority management, operation changes and milestones through OA, E-mail to remind relevant personnel, etc.

[0042] Preferably, the electronic parts information management system may include a data interface unit, a data extraction unit, a data cleaning unit, a data regularization unit, a data transformation unit, a data exploration unit and an information visualization and notification unit. The data interface unit is used to capture and input electronic parts information. The data extraction unit is used to obtain electronic parts identification. The data cleaning unit can process invalid information in the intermediate data file. The data regularization unit is used to normalize and check the consistency of the intermediate data file after data cleaning. The data transformation unit is used to output the electronic parts information form. Wherein, the electronic parts information form includes at least one of the engineering BOM, ERP BOM, and ECN. The data exploration unit is used to perform scheme design, parts optimization and procurement cost analysis on the electronic parts information form. The information visualization and notification unit is used to display the electronic parts management system and send information to relevant personnel.

[0043] The electronic parts information management system provided in this embodiment improves the work efficiency of BOM, ECN and ERP production methods and management, improves data accuracy and information visualization through automated processing, is conducive to the optimization of electronic parts in design schemes and the generation of design added value, and also saves the manpower and time costs of procurement decisions.

[0044] Example 2

[0045] This embodiment provides an electronic parts information management system, and this embodiment is a further improvement of embodiment 1, and repeated contents are not repeated. Preferably, the data interface unit adopts an application program interface. The data interface unit at least calls one of the voice, text, image, web page, and EDA tool interfaces to capture and input electronic parts information and generate a copy of the original interface data file. According to a preferred implementation, the data extraction unit converts the copy of the original interface data file into an intermediate data file in a unified format. The format of the original interface data file includes at least one of MP3, AAC, XLS, TXT, RTF, DOC, PDF, HTML, and PPT. The data extraction unit can identify the part identification carried in the corresponding format data. According to a preferred implementation, the data regularization unit performs data normalization and consistency check on the intermediate data file that has been cleaned by matching the electronic parts coding rules and query rules of the local predefined database to generate a final data file. According to a preferred implementation, the data conversion unit converts the final data file into an electronic parts information form in a corresponding format and outputs it.

[0046] Example 3

[0047] This embodiment provides an electronic parts information management system, and the electronic parts information management system provided by this embodiment is a further improvement of the electronic parts information management system involved in Example 2. The electronic parts information management system provided by this embodiment may include a data interface unit, a data extraction unit, a data cleaning unit, a data regularization unit, a data transformation unit, a data exploration unit, and an information visualization and notification unit.

[0048] The data interface unit is used to capture and input electronic component information. Preferably, the data interface unit can capture and input electronic component information by calling interfaces such as voice, text, image, web page, EDA tool, etc.

[0049] Preferably, the data interface unit can use an application programming interface (API). API is a set of rules and protocols for program calls. Programs interact and communicate through API interfaces to achieve data capture and service calls. Through API, database data can be obtained, functions of other databases and data formats can be obtained, and the automation and expansion of electronic parts information management systems can also be achieved.

[0050] Taking the web page as an example, the Python API interface is used to interact and communicate through the HTTP protocol. The HTTP protocol is a stateless TCP / IP application layer protocol that specifies the request and response format between the client and the server.

[0051] Based on Python and using Requests to process HTTP requests, it sends various types of HTTP requests such as GET and POST, and obtains response results; it uses the built-in HTML or XML parsing library Beautiful Soup to quickly parse web page content, and traverses the document tree through the API to implement the screening and extraction of electronic parts information in the web page.

[0052] #Install the BeautifulSoup library using the pip command:

[0053] pip install beautifulsoup4

[0054] #The example process of using BeautifulSoup to parse a web page is as follows:

[0055] ```Python

[0056] from bs4 import BeautifulSoup

[0057] soup=BeautifulSoup(html,"html.parser")

[0058] Among them, html is the HTML content of the target web page obtained through the requests library, and "html.parser" means using Python's built-in HTML parser for parsing. You can use a series of methods provided by BeautifulSoup to extract the required electronic parts data from the HTML page.

[0059] When obtaining information in an image file, OCR technology can be used to perform text recognition of electronic parts information in the image.

[0060] Take Python reading audio files as an example.

[0061] The #wavefile.read code example is as follows:

[0062] from scipy.io import wavfile

[0063] fs,audio=wavfile.read("0.wav")

[0064] print(type(audio))

[0065] The result is:

[0066] <class'numpy.ndarray'>

[0067] #soundfile.read code example is as follows:

[0068] import soundfile as sf

[0069] audio,fs=sf.read("0.wav")

[0070] print(type(audio))

[0071] The result is:

[0072] <class'numpy.ndarray'>

[0073] #librosa.load code example is as follows:

[0074] import librosa

[0075] audio,fs=librosa.load("0.wav")

[0076] print(type(audio))

[0077] The result is:

[0078] <class'numpy.ndarray'>

[0079] The data extraction unit is used to obtain the electronic component identification. The data extraction unit converts the original interface data file copy into an intermediate data file in a unified format. Preferably, the format of the original interface data file may include interface formats such as MP3, AAC, XLS, TXT, RTF, DOC, PDF, HTML, PPT, etc. Preferably, the data extraction unit can identify the component identification contained in the corresponding format data. For example, when the electronic component information entered by the data interface unit is in Excel format, the data extraction unit can identify the identification data containing the component information such as resistors R1, R2, capacitors C1, C2, etc. from the Excel data.

[0080] See also Figure 2 The input and output operations between the electronic parts information system and different database management systems also use intermediate data files. However, due to its unique file format, users generally cannot use it intuitively, and can only read and write using the specific interface provided by the electronic parts information management system.

[0081] Preferably, the unified format is an intermediate data format, the interface mode of the data file is an API interface, and the data format is converted into a specified format including: original data packet, XML, CSV, JSON and other formats through Python code, and the data between the electronic parts information systems communicate and exchange information in the form of the specified format. Generally, data in XML or CSV format has strong versatility, and each information system can recognize and process data received in this format.

[0082] The data extraction unit can obtain the electronic part identification through the intermediate data file by exporting the data of the original interface data file into an intermediate data file of a certain type and format, and then importing the data of the intermediate data file into the electronic part information management system. Common types of intermediate data files include text files (*.TXT), Excel tables (*.XLS) and XML files (*.XML). The text file method requires strict restrictions on the file format so that there will be no errors in saving and reading; and the Excel table method, because the Excel table is not friendly enough to the read and write interface compatibility of some programming languages, it needs to be accessed through the API provided by a special DLL, etc., resulting in restrictions on its format. XML files are widely used for their multiple advantages such as standardization, normalization, structuring and verifiability. Preferably, the intermediate data file of this embodiment can be an XML or CSV file.

[0083] XML documents are more suitable for storing BOM data. Almost all programming languages ​​provide convenient XML reading interfaces. Setting intermediate data files as XML files is conducive to the in-depth development of electronic parts information management systems and provides a wide range of selectivity during development.

[0084] Preferably, the data extraction unit may use regular expressions to extract the electronic part information in the intermediate data file, in particular, the part identification in the intermediate data file.

[0085] Regular expressions are a powerful text matching tool. Take the Python built-in re module as an example to match text from HTML pages and extract the required electronic parts information.

[0086] ```Python

[0087] import re

[0088] pattern = r'<a.*?href="(.*?)".*?> '

[0089] links=re.findall(pattern,html)

[0090] Among them, pattern is a regular expression pattern, .*? indicates non-greedy matching, and (.*?) indicates a group, matching the content in the brackets. The re.findall() function will search for all part information strings that match the pattern pattern in the html, such as resistor R, capacitor C, etc., and return a list links.

[0091] The data cleaning unit can process invalid information in the intermediate data file. Irrelevant or unusable original information can be defined as invalid information, for example, input errors, spelling errors, irregular electronic part names, inconsistent formats, duplicate values, missing values, abnormal values, invalid information due to the data structure and capture rules of the captured data information not meeting the processing requirements, etc. Specifically, abnormal values ​​such as 0 and O, irregular electronic part names such as a and A, - and _, and invalid space information. The number 0 and the letter O cannot be confused in the electronic part names and attribute values, and must be processed accurately.

[0092] Preferably, the data cleaning unit can process invalid information.

[0093] For example, Pandas is used to clean and process invalid information in the intermediate data files of the electronic parts information system.

[0094] #To install Pandas, you can use the pip command:

[0095] ```

[0096] pip install pandas

[0097] ```

[0098] #The basic process of using Pandas for data cleaning and processing is as follows:

[0099] ```Python

[0100] import pandas as pd

[0101] #Read CSV file

[0102] df = pd.read_csv("data.csv")

[0103] The query script data is parsed to obtain query condition data; and the query condition data is screened by a pre-set data processing engine to obtain the target query data.

[0104] Field specification verification includes field legitimacy verification, field validity verification and field integrity verification. Only when all three verifications are passed can the query field data be determined to be qualified query field data.

[0105] Field validity verification can include format verification, type verification, and security verification. Format verification is used to check whether the field conforms to the predefined part coding format requirements. Type verification is used to verify whether the field conforms to the expected data type. For example: integers, floating point numbers, part function description strings, etc. of part precision. Security verification is used to check whether the field contains potential malicious query risks. For example, SQL injection, script attacks, etc.

[0106] Field validity verification is used to ensure that the input data meets specific coding rules and requirements to avoid subsequent errors and problems. Field validity verification can include range verification and combinational logic verification. Range verification is used to verify whether the field value is within a predetermined range. For example, whether the amount of electronic parts used in a single machine is within a reasonable range, whether the price is within a valid range, etc. Combinatorial logic verification is used to verify whether the field value meets the requirements of a specific usage scenario. For example, whether the functional description, packaging, price, and accuracy of a certain electronic part meet specific logical relationships, etc.

[0107] The data regularization unit checks whether there are missing data items in the intermediate data file, analyzes whether the difference between the electronic part code entered in the intermediate data file and the electronic part code entered in the local predefined database is reasonable, and has different processing methods for various types of special parts. The processing methods are specifically divided into four types: adding, deleting, adjusting and decomposing. Figure 3 The data regularization unit generates a new BOM structure through adding, deleting, adjusting and decomposing algorithms. Figure 3 A, the data regularization unit can add parts groups to the original BOM structure through the addition algorithm to generate a new BOM structure. Figure 3B, the data regularization unit can delete the parts group in the original BOM structure through the deletion algorithm to generate a new BOM structure. Figure 3 C, the data regularization unit can adjust the combination logic of the parts group in the original BOM structure through the combination algorithm to generate a new BOM structure. Figure 3 D. The data regularization unit can decompose the parts group in the original BOM structure into new parts groups through a decomposition algorithm to generate a new BOM structure.

[0108] Special parts include key parts, outsourced parts, virtual parts, process parts, etc.

[0109] Key parts: Considering the product structure according to assembly requirements, the process separation surface to be divided, etc., it is necessary to refine the parts that are too coarse in the original design BOM during the process decomposition to generate components.

[0110] Outsourced parts: The component itself and all its components need to be processed by outsourcing, and its components will not appear in the process BOM.

[0111] Virtual parts: Parts that are defined in the process BOM and appear in the original design BOM, but are not manufactured or stored in actual production. Virtual parts will be deleted in the manufacturing BOM. By processing virtual parts, manufacturing work can be parallelized, thereby effectively utilizing resources when resources are sufficient.

[0112] Process parts: parts that do not appear in the original design BOM, but in actual production, due to process requirements, they must be manufactured and stored. Process parts will be added to the manufacturing BOM, and some parts in the process BOM will be downgraded to lower-level sub-parts of the process parts. These parts are called process sub-parts in the process BOM. By processing process sub-parts, manufacturing work can be serialized, which is conducive to saving resources.

[0113] The query rules of the local predefined database can be flexibly customized. Preferably, the query rules can include support for precise query, fuzzy query and combinational logic query, etc. Precise query, such as query by electronic part code, such as YER511R003; fuzzy query, such as classification by part function, such as resistor -> adjustable resistor -> fixed resistor -> high-precision high-power resistor -> lowercase r1 -> r11 -> uppercase R1 -> R111; combinational logic query, such as the logical AND or combination of the functional description, packaging, price and precision of a certain electronic part.

[0114] The data regularization unit classifies the part data in the intermediate data file according to the encoding rules of the local predefined database, including statistically merging the number of parts with the same encoding.

[0115] Preferably, the coding rules for electronic parts in this embodiment may include seven levels of classification and seven fields, each field is composed of different field values, and the coding format is: ABCDEFG, and each letter represents a first-level classification number.

[0116] The coding rules are explained in detail using fixed resistors of electronic devices:

[0117] A: Primary classification: (Major category) Y → Raw materials;

[0118] B: Secondary classification: (Type) E→Electronic devices;

[0119] C: Three-level classification: R → resistance;

[0120] D: Four-level classification: 51 → fixed resistor;

[0121] E: Five-level classification: (process) 1→SMT, 2→THR, 3→MNU

[0122] F: Six-level classification: (environmental protection properties) P→Pb, R→RoHS, X→ENV / NA

[0123] G: Seven-level classification: 001 (001-999, AAA-YYY) → serial number

[0124] Furthermore, the above four-level classification of the D field is described by the name defined according to the field value matching, and the rule definition for the four-level classification field value of the D field is 51 is as follows:

[0125] ※Specification description rules: Value, accuracy, power, packaging, process, environmental protection attributes

[0126] Value→(**.***K, **.***M, **.***R); Accuracy→±**%; Power→(*.*W, * / *W); Package→(0201, 0402, 0603, 1206); Process→(SMT, THR, MNU); Environmental properties→(Pb, RoHS)

[0127] ※Unit: PCS

[0128] For example, the detailed description of the electronic device corresponding to the code YER511R003 is: resistance value 33R, accuracy ±1%, power 1 / 16W, package 0201, process SMT, lead-free RoHS fixed resistor.

[0129] Preferably, the part information in the local predefined database includes but is not limited to part name, brand, model, parameters, price range, and procurement cycle.

[0130] The data conversion unit is used to output the electronic component information form. Preferably, the data conversion unit converts the final data file into an electronic component information form of a corresponding format according to the original design BOM and outputs the form.

[0131] The electronic parts information form in the corresponding format may be engineering BOM, ERP BOM, ECN, etc.

[0132] Preferably, the engineering BOM may include procurement BOM, manufacturing BOM, etc. The engineering BOM is created by the engineering team after detailed engineering analysis and optimization based on the original design BOM, including more specific information on components and subassemblies, such as specific suppliers, process parameters, costs, etc. The engineering BOM can provide more accurate information for product manufacturing and supply chain management.

[0133] Preferably, a purchasing BOM is generated from the original design BOM, and its rules are equivalent to a summary of purchased parts; a manufacturing BOM is generated from the original design BOM, and its rules are to expand the blanks and semi-finished products in the parts manufacturing process into the structure according to the process route of the parts.

[0134] The original design BOM and engineering BOM belong to the basic BOM category, which includes product design and engineering attributes. Other BOMs are converted based on the original design BOM and engineering BOM combined with information in specific application fields.

[0135] Since the original design BOM is the source, the engineering BOM and ERP BOM need to make structural adjustments, supplement and improve parts information based on the original design BOM, which is called BOM reconstruction.

[0136] The original design BOM is the BOM of the product in the design stage, which describes the initial design and conception of the product. The original design BOM is mainly created by the product design team, including the design of the overall structure, components and sub-assemblies of the product. The original design BOM usually contains detailed component information, size specifications and material requirements, providing a design basis for the manufacturing and assembly of the product. The original design BOM is the source of product data transmitted by the design department to the process, production, procurement and other departments.

[0137] ERP BOM is a bill of materials that can be recognized by the ERP system, and ERPBOM is a BOM dedicated to the ERP system.

[0138] The original design BOM divides the relationship between parts according to function, while the engineering BOM needs to be divided according to the work and assembly sequence. Therefore, the conversion from the original design BOM to the engineering BOM needs to be partially adjusted according to the process and production organization process, such as adjusting the related parts that were originally at the same level together and forming a parent-child relationship according to the assembly relationship. The mapping conversion mainly deals with virtual parts (parts that appear in the original design BOM but are not actually manufactured) and process parts (a part is manufactured separately or multiple parts are manufactured together due to equipment, materials, processability and other factors).

[0139] The data exploration unit performs scheme design, parts optimization and procurement cost analysis on the electronic parts information form.

[0140] The data exploration unit uses various analysis tools and methods to perform scheme design, part optimization and procurement cost analysis on electronic parts information forms.

[0141] The data exploration unit uses various analysis tools and methods to compare parameters of similar electronic parts, perform part normalization analysis, supplier concentration statistics, and usage statistics in electronic parts information forms, so as to facilitate design optimization and procurement cost analysis through electronic parts forms.

[0142] Preferably, the data exploration unit can use Python's Pandas and Numpy libraries to perform data analysis, that is, to perform scheme design and parts optimization and procurement cost analysis on the electronic parts information form. Data analysis includes field type analysis, variable distribution analysis, correlation analysis, missing value analysis, interactive analysis, data set comparison analysis, etc. For example, through the Pandas Profiling analysis tool, the analysis process can be completed by directly passing in DataFrame and the results can be displayed in HTML format, and the electronic parts information can be visually displayed in the form of reports, charts, etc.

[0143] For example, resistors R1 and R2 have the same resistance value, but different packages, 0402 and 0201, or different precision, 5% and 1%, or different suppliers or material processes, temperatures, and power tolerances, resulting in different prices. The amount of resistor R1 is 1000 and the unit price is 0.01 RMB, and the amount of resistor R2 is 1 and the unit price is 0.011 RMB. Normalizing resistors R1 and R2 can reduce the number of resistor codes to reduce storage, maintenance, and procurement costs.

[0144] The information visualization and notification unit is used to display the electronic parts management system and send information to relevant personnel. Preferably, the information visualization and notification unit uses drawing tools to intuitively present the electronic parts management system to enhance readability; and sends changes and milestones to relevant personnel through OA and E-mail. Preferably, the drawing tool can include a graphic plug-in and an extended data dictionary.

[0145] After the original design BOM is generated and exported by EDA tools such as Cadence, PADS, and AUTOCAD, the electronic parts information management system extracts, cleans, and organizes the original design BOM into a specific format of engineering BOM. The electronic parts information management system then imports the engineering BOM into the ERP system database, adds production and procurement information, and organizes the engineering BOM into an ERP BOM that can be directly imported into ERP. The electronic parts information management system can also generate ECN and part information change forms by comparing and changing engineering BOMs.

[0146] See also Figure 4 , the mapping and reconstruction process of design BOM, engineering BOM and ERPBOM includes:

[0147] S601: Inputting original design information from an EDA design tool;

[0148] S602: Importing a local predefined database;

[0149] S603: Generate design BOM;

[0150] S604: Output the design list summary;

[0151] S605: Adjust product structure and assembly unit;

[0152] S606: Add process division and sub-assembly parts;

[0153] S607: Data specification check, if it does not meet the rules, return to check the design BOM input in S603;

[0154] S608: Generate project BOM1;

[0155] S609: Compare the new project BOM2 with the existing project BOM1;

[0156] S610: Generate ECN and parts information change form;

[0157] S611: Engineering BOM1 includes and is used for electronic parts and assemblies, process components, process parameters, supplier models and optimization;

[0158] S612: Import the engineering BOM into the ERP system database;

[0159] S613: Divide production planning units;

[0160] S614: Check inventory and outsourcing processing data;

[0161] S615: Determine purchase and loss rate information;

[0162] S616: Add ERP code, supplier preference, and cost accounting information;

[0163] S617: Data specification check, if it does not meet the rules, return to check the engineering BOM imported in S612;

[0164] S618: Generate ERP BOM;

[0165] S619: The generated ERP BOM is used for warehouse inventory, production planning, outsourcing, purchasing and sales, cost accounting, etc.

[0166] Preferably, the ERP system database is based on the local predefined database and adds information such as ERP number, price, production, procurement and inventory, and financial management.

[0167] If you need to change the parts in the ERP BOM that has been imported into ERP again, you will need an ECN engineering change file.

[0168] The EDA tool exports the changed project BOM.

[0169] The electronic parts information management system compares the changed engineering BOM exported by the EDA tool with the previous engineering BOM, and organizes it into an ECN engineering change file in a specific format; then imports the changes in the ECN engineering change file into the ERP BOM to complete the electronic parts change.

[0170] The use of electronic parts information management system can effectively improve BOM output efficiency, reduce the entry and comparison of complex information, and only enter useful information, which can reduce the chance of human errors.

[0171] The electronic parts information management system provided in this embodiment greatly improves efficiency and accuracy by extracting, cleaning and regularizing data in the electronic parts information management system during the process of classifying, merging, sorting and comparing the original design BOM.

[0172] The operations involving BOM in existing manufacturing include:

[0173] S100: Create raw format BOM data using EDA software;

[0174] S200: Generate engineering BOM using original BOM;

[0175] S300: Generate ERP BOM using engineering BOM;

[0176] S400: Use EDA software to create the original BOM that has been modified twice or more;

[0177] S500: Generate ECN using the original BOM of S400;

[0178] S600: Import ECN into ERPBOM.

[0179] The electronic parts information management system provided in this embodiment can be applied to S200 / S300 / S500.

[0180] Example 4

[0181] This embodiment provides a method for converting the original design BOM data in the original format created by EDA software into an engineering BOM using the electronic parts information management system involved in Embodiment 3.

[0182] The original design BOM data created by EDA software can be the original design BOM (Excel format) containing the part information exported after batch input of material information such as "part code", "quantity", "number", "attribute", etc. by EDA tools through specific settings to edit the properties of a single part and delete useless part description information in batches.

[0183] The electronic parts information management system provided in this embodiment can check, sort, classify, merge, etc. the material information in the original design BOM, extract the corresponding information in the system library file, and organize it into a specific format of the engineering BOM.

[0184] The original design BOM (Design BOM) is the BOM of the product in the design stage, which is used to describe the initial design and concept of the product.

[0185] The Engineering BOM is created by the engineering team after detailed engineering analysis and optimization based on the original design BOM, including more specific component and sub-assembly information.

[0186] See also Figure 5 Preferably, using the electronic parts information management system to convert the original design BOM data in the original format created by the EDA software into the engineering BOM includes at least the following steps:

[0187] S201: Import the original design BOM. The data interface unit communicates interactively with the interface such as the EDA tool by calling the API and imports the original design BOM. The data extraction unit converts the original format BOM into the intermediate file data in a unified format. The data extraction unit extracts the identification data of the electronic parts information such as resistors R1, R2, capacitors C1, C2 and other parts information contained in the intermediate data file. The data cleaning unit cleans the invalid information in the intermediate data file such as abnormal values ​​such as 0 and O, irregular names such as a and A, - and _, and invalid space information.

[0188] S202: The data regularization unit checks whether the original design BOM is qualified. If not, the operation is stopped, and the information visualization and notification unit prompts or requires to re-import the original design BOM; if qualified, the design BOM is generated and step S203 is executed.

[0189] S203: The data conversion unit creates an Excel file and BOM file name for the new project BOM.

[0190] S204: The data conversion unit copies the design BOM content to the new BOM form and sorts it.

[0191] S205: The data regularization unit checks whether there are duplicate material numbers in the new BOM form; if there are duplicate materials, the operation is stopped, and the data exploration unit prompts the supplier model to be preferred. Preferably, the data exploration unit checks the new BOM form and prompts the process parameters and supplier model to be preferred. The information visualization and notification unit prompts or requires the original design BOM to be re-imported.

[0192] S206: The data conversion unit adjusts the product process and assembly unit of the design BOM, adds subassemblies, and automatically adds serial numbers.

[0193] S207: The data conversion unit copies the content of the corresponding part number in the database "ADS PN data table.xls" to the new BOM form;

[0194] S208: The data conversion unit copies the content of the corresponding part number in the table "Mfg PN table.xls" to the new BOM form;

[0195] S209: The data regularization unit performs a data regularity check on the new BOM form again, and if it passes, the project BOM generation is completed.

[0196] Example 5

[0197] This embodiment provides a method for converting a project BOM into an ERP BOM using the electronic parts information management system involved in Embodiment 3.

[0198] ERPBOM is a bill of materials that can be recognized by the ERP system, and ERPBOM is a BOM dedicated to the ERP system.

[0199] See also Figure 6 Preferably, the method of converting the engineering BOM into the ERP BOM using the electronic parts information management system at least includes:

[0200] S301: Import the engineering BOM into the electronic parts information management system through the data interface unit. Use the data extraction unit to obtain the electronic parts information in the engineering BOM, and use the data cleaning unit to process the invalid information in the electronic parts information. The data conversion unit calls the local ERP database to divide the production planning unit and processes the parts inventory and outsourcing processing data to determine the purchase volume and loss rate of electronic parts.

[0201] S302: The data conversion unit creates an Excel file and BOM file name for ERPBOM.

[0202] S303: The data conversion unit copies the project BOM content to the new BOM form.

[0203] S304: The data conversion unit automatically adds ERP code and cost accounting information in the new BOM form.

[0204] S305: The data conversion unit adds the order number, main part number, document date, and work order type to the new BOM table.

[0205] S306: The data regularization unit performs a data regularity check on the new BOM form again, and generates ERPBOM if it passes.

[0206] Example 6

[0207] This embodiment provides a method for generating ECN using the electronic parts information management system involved in Embodiment 3.

[0208] See also Figure 7 Preferably, the method for generating ECN using the electronic parts information management system comprises at least the following steps:

[0209] S501: Import project BOM1 and project BOM2. Import the project BOM into the electronic parts information management system through the data interface unit; use the data extraction unit to process the electronic parts information in the project BOM, and use the data cleaning unit to process the invalid information in the electronic parts information. Preferably, the data interface unit interacts with the interface such as the EDA tool by calling the API and imports the project BOM, the data extraction unit converts the project BOM into intermediate file data in a unified format, the data extraction unit extracts the identification data of the electronic parts information such as resistors R1, R2, capacitors C1, C2 and other parts information contained in the intermediate data file, and the data cleaning unit cleans the invalid information in the intermediate data file such as abnormal values ​​such as 0 and O, irregular names such as a and A, - and _, and invalid space information.

[0210] S502: Check whether BOM is qualified. The data regularization unit checks whether the imported engineering BOM is qualified. If not, return to S501 and re-import the engineering BOM.

[0211] S503: Add ECN number, identify applicant, and editor. Add ECN number, identify applicant, and editor to the electronic parts information management system through the data conversion unit.

[0212] S504: Create Excel and ECN file names. The data conversion unit creates an ECN file name in Excel format.

[0213] S505: Compare engineering BOM1 with engineering BOM2. Use the data conversion unit to compare engineering BOM1 with engineering BOM2. The data conversion unit generates a part information change form based on the differences between the engineering BOMs.

[0214] S506: Copy the comparison difference content to a new Excel table and sort it. Use the data conversion unit to copy the engineering change content to a new Excel table and sort it.

[0215] S507: Automatically add filling sequence number. Automatically add filling sequence number by using data conversion unit.

[0216] S508: Copy the content in the table "ADS PN data table.xls". Use the data conversion unit to copy the content of the corresponding part number in the database "ADS PN data table.xls" to the new Excel form.

[0217] S509: Copy the content in the table "Mfg PN table.xls". Use the data conversion unit to copy the content of the corresponding part number in the database "Mfg PN table.xls" to the new Excel form.

[0218] S510: Generate ECN. After the data regularization unit performs a data regularity check on the Excel form again, the ECN generation is completed.

[0219] Preferably, the project BOM1 and the project BOM2 represent the new project BOM and the old project BOM respectively. The data conversion unit generates the ECN according to the difference between the new project BOM and the old project BOM.

[0220] Preferably, after generating the ECN, the electronic parts information management system can also import the changes in the ECN engineering change file into the ERP BOM to complete the change of the electronic parts form information.

[0221] Example 7

[0222] This embodiment provides an electronic component information management method. Preferably, the electronic component information management method provided by this embodiment can be implemented using the electronic component information management systems described in Embodiment 1, Embodiment 2, and Embodiment 3.

[0223] See also Figure 8 Preferably, the electronic parts information management method provided in this embodiment may include the following steps:

[0224] S001: Initialize the data interface unit. Capture electronic parts information by calling voice, text, image, web page and other interfaces.

[0225] S002: Extraction of electronic parts information. Process and convert the original interface data file copies, and convert the original interface data file copies in different formats (such as MP3, AAC, XLS, TXT, RTF, DOC, PDF, HTML, PPT and other interface data formats) into intermediate data files in a unified format.

[0226] S003: Clean the data. Specifically, process the invalid information contained in the electronic component information. The invalid information in the electronic component information includes: the electronic component name is not standardized, the format is inconsistent, or there are repeated values, missing values, abnormal values ​​and other information.

[0227] S004: Regularize the data. By calling the above intermediate data file to query the local predefined database, each part in the intermediate data file is matched with the latest electronic part data in the local predefined database, and the name and code of each electronic part in the intermediate data file is supplemented with the latest part data in the local predefined database to generate a final data file.

[0228] S005: Transform the data. The above-mentioned local predefined database is called, and the electronic component information form in the corresponding format is automatically generated and output through the pre-defined conversion rules and baselines.

[0229] S006: Conduct data exploration. Use various analysis tools and methods to conduct scheme design, parts optimization and procurement cost analysis on electronic parts information forms.

[0230] S007: Information visualization and notification. Use drawing tools to visualize the electronic parts management system and enhance readability; send changes and milestones to relevant personnel through OA and E-mail.

[0231] Example 8

[0232] This embodiment provides a storage medium on which a readable computer program is stored. When the computer program is executed by a processor, the electronic parts information management system described in Embodiment 1, Embodiment 2 and Embodiment 3 can be run.

[0233] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modification, equivalent replacement and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention. The electronic parts information management system described in Embodiment 1, Embodiment 2 and Embodiment 3 can be run at the same time.

[0234] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. An electronic parts information management system, characterized in that: include: Data interface unit, used to capture and input electronic parts information; A data extraction unit, used to obtain electronic component identification and generate an intermediate data file; A data cleaning unit, used for processing invalid information in the intermediate data file; Data regularization unit, used to normalize and check the consistency of intermediate data files after data cleaning; A data conversion unit, used to output an electronic parts information form; wherein the electronic parts information form includes at least one of an engineering BOM, an ERP BOM, and an ECN; The data exploration unit is used to perform scheme design, parts optimization and procurement cost analysis on electronic parts information forms.

2. An electronic parts information management system according to claim 1, characterized in that: The data interface unit adopts an application program interface; The data interface unit at least calls one of voice, text, image, web page, and EDA tool interface to capture and input electronic component information and generate a copy of the original interface data file.

3. An electronic parts information management system according to claim 2, characterized in that: The data extraction unit converts the original interface data file copy into an intermediate data file of a unified format; The format of the original interface data file includes at least one of MP3, AAC, XLS, TXT, RTF, DOC, PDF, HTML, and PPT; The data extraction unit can identify the part identification contained in the corresponding format data.

4. An electronic parts information management system according to claim 3, characterized in that: The data regularization unit performs data normalization and consistency check on the intermediate data file after data cleaning by matching the electronic parts coding rules and query rules of the local predefined database to generate a final data file.

5. An electronic parts information management system according to claim 3, characterized in that: The data conversion unit converts the final data file into an electronic component information form of a corresponding format and outputs it.

6. A method for using an electronic parts information management system, characterized in that: The original design BOM data in the original format created by the EDA software is converted into the engineering BOM using the electronic parts information management system as claimed in any one of claims 1 to 5.

7. A method for using an electronic parts information management system, characterized in that: The engineering BOM is converted into the ERP BOM using the electronic parts information management system as claimed in any one of claims 1 to 5.

8. A method for using an electronic parts information management system, characterized in that: The ECN is generated using the electronic parts information management system as claimed in any one of claims 1 to 5.

9. An electronic parts information management method, characterized in that: Implemented by using the electronic parts information management system as claimed in any one of claims 1 to 5; The electronic parts information management method comprises the following steps: S001: Data interface unit initialization; S002: Electronic parts information extraction; S003: Clean the data; S004: Regularize the data; S005: transform the data; S006: Conduct data exploration; S007: Information visualization and notification.

10. A storage medium having a readable computer program stored thereon, characterized in that: When the computer program is executed by a processor, the processor performs the method according to any one of claims 6 to 9.

Images