A method and system for collecting supply chain data

Abstract

The present application provides a method and system for collecting supply chain data, the method comprising: obtaining a corresponding data supply maturity based on feedback information provided by a target supplier to a chain owner, and determining a data docking maturity based on the feedback information, wherein the target supplier and the chain owner are located in the same supply chain; determining target collection parameters based on the feedback information and the data supply maturity; determining a target collection method based on confirmation information provided by the target supplier and the data docking maturity; acquiring corresponding target data based on the target collection method and the target collection parameters. The present application improves the comprehensiveness of supplier-related data, thereby reducing the risk of the chain owner.

Description

Technical Field

[0001] The present application relates to the field of data processing, and specifically to a method and system for collecting supply chain data. Background Art

[0002] The supply chain system is aimed at manufacturers, suppliers, distributors, retailers, logistics companies, end users and other users. It realizes the whole chain management from production end to consumption end from sales, procurement, suppliers, inventory, logistics and other links, optimizes the allocation of enterprise resources, and promotes efficient collaboration between upstream and downstream of the industrial chain.

[0003] Supply chain leaders refer to core enterprises that occupy a dominant position in the entire supply chain, have a strong direct or indirect influence on the resource allocation and application of the entire supply chain or most enterprises in the supply chain, pay the strongest attention to the value realization of the entire supply chain, and shoulder the important task of improving the performance of the entire supply chain. Supply chain leaders are mostly terminal product manufacturers that are at the downstream of the supply chain, close to the consumer market, but at the same time have super strength in brand influence, R&D capabilities, marketing methods, etc. Therefore, supply chain leaders need to obtain supplier-related data and build a supply chain ecosystem to facilitate data management.

[0004] However, suppliers will only record the business information or production information required by each link in a targeted manner, and all of this information is determined by their respective parties. For the information held by one party, the chain owner cannot understand the required supplier-related data. Some suppliers even do not allow data collection services on the grounds of data security, resulting in data loss. Summary of the invention

[0005] The present application provides a supply chain data collection method and system to provide chain owners with comprehensive supplier-related data and create a supply chain ecosystem to facilitate data management while reducing chain owner risks.

[0006] In a first aspect, the present application provides a method for collecting supply chain data, comprising the steps of:

[0007] Assess the maturity of the data to be provided, where the data to be provided is the data required by the chain owner and allowed to be provided by the target supplier;

[0008] Determining data collection content according to the data to be provided;

[0009] Determine the data collection and connection method corresponding to the data to be provided according to the needs of the target supplier;

[0010] According to the data acquisition docking mode, target data corresponding to the data acquisition content is acquired.

[0011] In some embodiments, the step of assessing the maturity of the data to be provided comprises:

[0012] Obtaining the number of types of data to be provided by the target supplier;

[0013] The maturity is determined according to the number of species, and the maturity is positively correlated with the number of species.

[0014] In some embodiments, the step of determining data collection content according to the data to be provided includes:

[0015] According to the data to be provided, corresponding collection fields, collection frequency and number of retries for collection failure are set;

[0016] A corresponding collection scope is set according to the data to be provided and the input information provided by the target supplier.

[0017] In some embodiments, the step of determining the data collection and docking mode corresponding to the data to be provided according to the needs of the target supplier includes:

[0018] If the target supplier selects the data collection and connection mode as the first type, the data collection and connection mode is set to deploy an agent service component on the third server 30, and obtain the target data through the agent service component.

[0019] In some embodiments, it also includes: if the first database of the third server 30 does not support the proxy service component to collect data, converting the corresponding data of the first database into the corresponding data of the second database, obtaining the target data from the second database, and the second database supports the proxy service component to collect data.

[0020] In some embodiments, the step of determining the data collection and docking mode corresponding to the data to be provided according to the needs of the target supplier includes:

[0021] If the target supplier selects the data collection and connection mode as the second type, the data collection and connection mode is set to obtain the target data from a third-party server rented by the target supplier through an application program interface.

[0022] In some embodiments, the step of determining the data collection and docking mode corresponding to the data to be provided according to the needs of the target supplier includes:

[0023] If the target supplier selects the data collection and connection mode as the third type, the data collection and connection mode is set to receive the target data through a message push component.

[0024] In some embodiments, the step of acquiring target data corresponding to the data collection content according to the data collection docking mode includes the following steps:

[0025] Performing data cleaning on the target data and outputting the cleaned target data;

[0026] The cleaned target data is normalized to obtain target data that conforms to the data format of the chain master service.

[0027] In some embodiments, after acquiring the target data corresponding to the data collection content according to the data collection docking mode, the method further includes the following steps:

[0028] Sending the target data to a first server used by a target chain owner; the target chain owner and the target supplier are located in the same supply chain;

[0029] Wherein, the target data is encrypted before transmission.

[0030] In a second aspect, the present application also provides a data acquisition system, comprising:

[0031] An evaluation module, used to evaluate the maturity of the data to be provided, where the data to be provided is the data required by the chain owner and allowed to be provided by the target supplier;

[0032] A processing module, used to determine data collection content according to the data to be provided, and determine a data collection docking method corresponding to the data to be provided according to the needs of the target supplier;

[0033] The acquisition module is used to acquire target data corresponding to the data acquisition content according to the data acquisition docking mode.

[0034] The supply chain data collection method and system provided in the present application evaluates the data docking maturity and data supply maturity, and the feedback information is the data required by the chain owner and allowed to be provided by the target supplier; the data collection content is determined according to the feedback information; the data collection method corresponding to the feedback information is determined according to the needs of the target supplier; the target data corresponding to the data collection content is acquired according to the data collection method, and different data collection methods can be set according to the different data management situations of the suppliers, so that the suppliers can meet the data collection needs of the chain owner, improve the comprehensiveness of the supplier-related data, and thus reduce the risks of the chain owner. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0036] Figure 1 This is a flow chart of a method for collecting supply chain data provided in an embodiment of the present application;

[0037] Figure 2 This is a schematic diagram of a scenario of the supply chain data collection method provided in an embodiment of the present application;

[0038] Figure 3 This is another scenario schematic diagram of the supply chain data collection method provided in an embodiment of the present application;

[0039] Figure 4 This is another scenario schematic diagram of the supply chain data collection method provided in an embodiment of the present application;

[0040] Figure 5 This is another scenario diagram of the supply chain data collection method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0042] In the description of the embodiments of the present application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0043] In order to enable any person skilled in the art to implement and use the present application, the following description is provided. In the following description, details are listed for the purpose of explanation. It should be understood that those of ordinary skill in the art can recognize that the present application can also be implemented without using these specific details. In other examples, the known process will not be elaborated in detail to avoid unnecessary details that make the description of the present application embodiment obscure. Therefore, the present application is not intended to be limited to the embodiments shown, but is consistent with the widest range of principles and features disclosed in accordance with the embodiments of the present application.

[0044] In recent years, supply chain capabilities have become increasingly important as the core competitiveness of enterprises. As the ultimate bearer of all these impacts, the chain leader needs to bear the pressure from the market. Therefore, improving the risk resistance of its own supply chain and establishing a highly resilient supply chain is the best way to cope with current market changes. Leading companies have created a system based on real-time data and algorithms to evaluate the level of suppliers' own management capabilities. Through this system, the delivery risk, quality risk and cost risk of the supply chain can be accurately evaluated or assessed. Based on the evaluation results, the required suppliers are screened and close cooperative relationships are established with them to share information and resources in order to quickly respond to problems and find solutions. However, the problems with the system established by the chain leader to evaluate the level of suppliers' own management capabilities are:

[0045] Heterogeneity of data types: Different suppliers and different production equipment are diverse, so there are a large number of different types of data formats, including structured, semi-structured, and unstructured data.

[0046] Heterogeneity of data quality: Due to the uneven level of informationization of suppliers, a large amount of noisy data will be generated during the data collection process when connecting with suppliers, and the data needs to be processed, cleaned, and handled.

[0047] Diversity of docking systems: The types of systems used or purchased by different suppliers are also diverse, including privately deployed systems, Software as a Service (SaaS) cloud products, local paper documents, etc.; therefore, multiple forms of data docking are required.

[0048] Comprehensiveness of data and trust issues in data provision: Suppliers are concerned about the risk of key data leakage during the data collection process, or they do not approve of the data collection method (such as not wanting to deploy some content on their own servers), which leads to not allowing or refusing to provide the chain owner with the data they need.

[0049] The following describes the supply chain data collection method and system of the present application in conjunction with the accompanying drawings to solve the above-mentioned problems.

[0050] The execution subject of the method for collecting supply chain data in the embodiment of the present application can be the data collection system provided in the embodiment of the present application. For example, the method for collecting supply chain data provided in the embodiment of the present application can be applied to the data collection system. Among them, the data collection system can be deployed on the first server 20 used by the chain owner of the supply chain, the data collection system can also be deployed on the third server 30 used by the supplier of the supply chain, and the data collection system can be deployed on the second server 10 that provides data transfer and processing services, and the second server 10 is a third-party server trusted by both the chain owner and the supplier of the supply chain. The above-mentioned first to third servers 30 can be independent servers, or they can be a server network or server cluster composed of servers, which includes but is not limited to computers, network hosts, single network servers, multiple network server sets or servers composed of multiple servers. Among them, the server is composed of a large number of computers or network servers based on cloud computing (Cloud Computing). It can be understood by those skilled in the art that the above-mentioned application scenario is only an application scenario of the present application solution, and does not constitute a limitation on the application scenario of the present application solution. It can be understood that the data collection system can also include one or more other servers, which are not specifically limited here.

[0051] Reference Figure 1 As shown, Figure 1 is a flow chart of a supply chain data collection method provided in an embodiment of the present application. Figure 1 The flowcharts shown in the figures or other figures show a logical order, but in some cases, the steps shown or described may be performed in a different order than that shown in the figure. The supply chain data collection method provided in the embodiment of the present application is applied to any end of the first server 20, the second server 10 and the third server 30, and the supply chain data collection method includes the steps of:

[0052] S100. Evaluate and obtain corresponding data supply maturity based on feedback information provided by the target supplier to the chain owner, and determine data docking maturity based on the feedback information. The target supplier and the chain owner are located in the same supply chain.

[0053] Specifically, the supply chain refers to a network structure of a series of organizations, personnel, activities, information and resources involved in the entire process from raw material procurement to the final consumer. It covers the entire process from raw material acquisition, production and manufacturing, logistics and transportation, distribution to final delivery to consumers. The main roles usually included in the supply chain are suppliers (i.e. companies or individuals who provide raw materials or parts), manufacturers / producers (companies that process raw materials into finished products), distributors / retailers (responsible for distributing products to the terminal market, usually retail stores or wholesalers), customers / consumers (individuals or companies that ultimately use products or services). The chain leader of the supply chain refers to the company that occupies a dominant position in the entire supply chain, has a strong direct or indirect influence on the resource allocation and application of the entire supply chain or most companies in the supply chain, and pays the strongest attention to the value realization of the entire supply chain, and shoulders the important task of improving the performance of the entire supply chain. Chain leader companies can include technology and R&D leading companies (such companies are usually the technology center of the industrial chain, formulate the rules and standards of the industrial chain, and obtain most of the value, such as Intel, Apple, Lenovo in the IT product field, etc.), as well as companies with outstanding brand and channel advantages (such companies belong to the market center of the industrial chain, closer to the downstream of the industrial chain, and their core lies in brand influence and market channel control, such as Walmart and Carrefour in the fast-moving consumer goods industry). Target suppliers are suppliers that chain leaders in a supply chain are concerned about, suppliers that need to be observed, or suppliers with whom they have established cooperation. The number of target suppliers can be one or more. Feedback information is the supplier-related data that any target supplier can provide to the chain leader and that the chain leader hopes to master. The corresponding data supply maturity can be evaluated based on the feedback information provided by the target supplier to the chain leader, and the data docking maturity can be evaluated based on the feedback information provided by the target supplier to the chain leader. Among them, the target supplier and the chain leader are in the same supply chain.

[0054] For specific implementation means of evaluating the data supply maturity of the target supplier based on the feedback information, please refer to steps S110-S120 of the embodiment below. For specific implementation means of evaluating the data supply maturity of the target supplier based on the feedback information, please refer to steps S110-S120 of the embodiment below.

[0055] In some embodiments, the feedback information includes the data to be provided that the target supplier allows to be provided to the chain owner; the step of evaluating and obtaining the corresponding data supply maturity according to the feedback information provided by the target supplier to the chain owner includes:

[0056] S110, obtaining the data type and quantity of the data that the target supplier is allowed to provide to the chain owner according to the data to be provided;

[0057] S120. Determine the data supply maturity according to the data type and the number of types.

[0058] Specifically, the feedback information may include the data to be provided that the target supplier allows to be provided to the chain owner. The data to be provided includes multiple data types, including but not limited to quality data, capacity data, inventory data, logistics data, production plan, R&D capabilities and supply data. Quality data includes but is not limited to yield rate, process quality monitoring data, equipment operation data, equipment overall efficiency (Overall Equipment Effectiveness, OEE), environmental monitoring data, process parameters and program files. Capacity data includes but is not limited to output data, real-time output, daily output, personnel information, scheduling information, and operating rate. Inventory data includes but is not limited to raw material inventory, multi-level inventory, shipment quality and inventory. Logistics data includes but is not limited to supply data includes but is not limited to transportation management system data (Transportation Management System, TMS data) and inventory.

[0059] The chain owner can initiate a data collection request to the target supplier. The data collection request includes the identity information of the target supplier and the data collection content required by the chain owner. In this way, the target supplier can obtain the data collection request and select the data to be provided or uploaded to the chain owner according to the data collection content therein. The data type of the corresponding data can be obtained according to the name or content of the data included in the data to be provided, and then the number of different data types in all the data to be provided is counted to obtain the number of types. After that, the data supply maturity of the data to be provided that the target supplier can upload to the chain owner is obtained based on the number of types and data types.

[0060] In some embodiments, the step of determining the data supply maturity according to the data type and the number of types includes:

[0061] S121, querying a preset relationship table according to the data type to obtain a data importance level corresponding to the data type, and determining a first maturity parameter according to the data importance level corresponding to the data type; the preset relationship table includes a corresponding relationship between the data type and the data importance level, and the first maturity parameter is positively correlated with the data importance level;

[0062] S122, determining a second maturity parameter according to the number of species, where the second maturity parameter is positively correlated with the number of species;

[0063] S123. Perform weighted calculation according to the first maturity parameter and the second maturity parameter to obtain the corresponding data supply maturity.

[0064] Specifically, the preset relationship table includes the corresponding relationship between at least two data types and multiple data importance levels in the embodiment corresponding to steps S110-S120 above, one data importance level corresponds to multiple data types, and one data type corresponds to one data importance level. Among them, since a supply chain may include a chain owner and multiple target suppliers, the preset relationship tables queried by a chain owner and multiple target suppliers of the same supply chain may be the same or different, and the preset relationship tables queried by multiple chain owners of multiple supply chains and the same target supplier may be the same or different. The present application can query the preset relationship table according to one of the data types of the data to be provided to obtain its corresponding data importance level, and then calculate the first maturity parameter according to the data importance level corresponding to the data type. Among them, the first maturity parameter is positively correlated with the data importance level of the data to be provided, that is, the higher the data importance level corresponding to the data type, the larger the first maturity parameter corresponding to the data to be provided, and conversely, the lower the data importance level corresponding to the data type, the smaller the first maturity parameter corresponding to the data to be provided. In addition, the second maturity parameter is positively correlated with the number of types of data to be provided, that is, the more types of data to be provided, the larger the second maturity parameter of the data to be provided, and conversely, the fewer types of data to be provided, the smaller the second maturity parameter of the data to be provided.

[0065] Exemplarily, it is assumed that the types of supplier-related data of the target supplier required by the chain owner include quality data, capacity data, inventory data and logistics data, and the chain owner sets the data importance levels of these four types of data to α1, α2, α3, and α4 respectively in advance, and these four data importance levels are all greater than 0 and α1+α2+α3+α4=1, and a constant β is set. If the target supplier can report only any one of the quality data, capacity data, inventory data and logistics data to be provided, then the first maturity parameter is L1, which is equal to the product of the data importance level corresponding to any one of the above supplier-related data and the constant β. If the target supplier can report any two of the quality data, capacity data, inventory data and logistics data to be provided, then the first maturity parameter is L2, which is equal to the sum of the product results of the data importance levels corresponding to any two of the above supplier-related data and the constant β. For example, if the data to be provided are only quality data and capacity data, then its first maturity parameter L2=α1×β+α2×β. If the target supplier can only report any three of the data to be provided, including quality data, capacity data, inventory data, and logistics data, then the first maturity parameter is L3, which is equal to the sum of the product of the data importance levels corresponding to any three of the above supplier-related data and the constant β. If the target supplier can report four types of data to be provided, including quality data, capacity data, inventory data, and logistics data, then the first maturity parameter is L4=α1×β+α2×β+α3×β+α4×β. Among them, L4>L3>L2>L1.

[0066] Exemplarily, it is assumed that the types of supplier-related data of the target supplier required by the chain owner include quality data, production capacity data, inventory data and logistics data. If the target supplier can report only any one of the quality data, production capacity data, inventory data and logistics data, the second maturity parameter is W1. If the target supplier can report only any two of the quality data, production capacity data, inventory data and logistics data, the second maturity parameter is W2. If the target supplier can report only any three of the quality data, production capacity data, inventory data and logistics data, the second maturity parameter is W3. If the target supplier can report four types of feedback information, including quality data, production capacity data, inventory data and logistics data, the second maturity parameter is W4. Among them, W4>W3>W2>W1.

[0067] In addition, the weight coefficients of the first maturity parameter and the second maturity parameter are set to A1 and A2 respectively, and the sum of the weight coefficients of the first maturity parameter and the second maturity parameter is equal to 1, that is, A1+A2=1. Then, according to the first maturity parameter L and the weight coefficient A1, the second maturity parameter W and the weight coefficient A2, a weighted calculation is performed to obtain the corresponding data supply maturity, that is, data supply maturity = first maturity parameter L*weight coefficient A1+second maturity parameter W*weight coefficient A2.

[0068] In some embodiments, the feedback information includes the data collection method in which the target supplier supports the chain owner to collect data; the step of determining the maturity of data docking according to the feedback information includes:

[0069] S150: If the data collection method includes at least the first collection method, determine that the data connection maturity is the first connection maturity;

[0070] S160: If the data collection method includes at least the second collection method and does not support the first collection method, determine that the data connection maturity is the second connection maturity;

[0071] S170: If the data collection method is the third collection method, determine that the data connection maturity is the third connection maturity;

[0072] The first docking maturity is greater than the second docking maturity, and the second docking maturity is greater than the third docking maturity.

[0073] Specifically, the data collection method includes but is not limited to a first collection method, a second collection method and a third collection method. The first collection method is an Agent deployment collection method, the second collection method is an API interface collection method, and the third collection method is an EMQ collection method.

[0074] The data collection method at least includes the first collection method, that is, the data collection method includes the first situation that the target supplier supports the first collection method but does not support the second collection method and the third collection method, the data collection method includes the second situation that the target supplier supports the first collection method and the second collection method but does not support the third collection method, and the data collection method includes the third situation that the target supplier supports the first collection method, the second collection method and the third collection method. In this way, if the data collection method in the feedback information provided by the target supplier to the chain owner includes at least the first collection method, then its data docking maturity is the first docking maturity.

[0075] The data collection method at least includes the second collection method and does not support the first collection method, that is, the data collection method includes the fourth situation that the target supplier supports the second collection method but does not support the first collection method and the third collection method, and the fifth situation that the target supplier supports the second collection method and the third collection method but does not support the first collection method. In this way, if the data collection method in the feedback information provided by the target supplier to the chain owner includes at least the second collection method and does not support the first collection method, then its data docking maturity is the second docking maturity.

[0076] The data collection method is the third collection method, that is, the data collection method includes the sixth situation that the target supplier supports the third collection method but does not support the first collection method and the second collection method. In this way, if the data collection method in the feedback information provided by the target supplier to the chain owner is the third collection method, then its data docking maturity is the third docking maturity.

[0077] It should be noted that, in this application, there is no order of precedence for the step of evaluating the corresponding data supply maturity based on the feedback information provided by the target supplier to the chain owner, and the step of determining the data docking maturity based on the feedback information. The two can be executed simultaneously or one after the other.

[0078] S200: Determine target acquisition parameters according to the feedback information and the data supply maturity.

[0079] The specific target acquisition parameters are essentially the data acquisition content and acquisition strategy. The target acquisition parameters can be determined according to the type or category of the data to be collected. For the specific process of determining the target acquisition parameters, please refer to the embodiments S210-S220 below.

[0080] In some embodiments, the step of determining target acquisition parameters according to the feedback information and the data supply maturity includes:

[0081] S210, setting corresponding index fields and data collection strategies according to the feedback information and the data supply maturity, wherein the data collection strategies include collection frequency and number of retries for collection failure;

[0082] S220, setting a corresponding collection scope according to the feedback information and the input information provided by the target supplier;

[0083] Wherein, the target acquisition parameter includes the index field; or,

[0084] The target acquisition parameter includes the index field and the target acquisition parameter further includes at least one of a data acquisition strategy and the acquisition range.

[0085] Specifically, the index field is used to search and collect or capture the keywords or key fields corresponding to different types of data to be provided, that is, each type of data to be provided is set with its own independent index field, and the number of index fields can be one or more. The collection frequency is the frequency or frequency used to collect target data. The number of retries for failed collection is the maximum number of times to re-collect after the collection of target data fails. For example, after the collection of target data fails according to a certain index field, you can try to collect it again. If the number of failures reaches the preset number threshold, you can be prompted to replace the new index field. The present application can set corresponding index fields according to the data to be provided and the maturity of the data supply in the feedback information, and formulate corresponding data collection strategies according to the feedback information provided by the target supplier to the chain owner. In addition, the collection scope is also the scope within which data search and collection are allowed. For example, the target supplier has multiple databases, and the data in some databases may be private or cannot be searched and collected due to confidentiality reasons. Therefore, the input information of the target supplier can be obtained. The input information includes the ID of a database that needs to be kept confidential corresponding to a certain type of data to be provided. In this way, the collection scope can be set according to the type of data to be provided and the input information. The set collection scope can be the ID or address of a database that does not need to be kept confidential and allows data collection, so that this part of the database that needs to be kept confidential can be shielded during subsequent data collection, thereby improving the security of the target supplier.

[0086] Exemplarily, the index field may include the field name, field type and field comment.

[0087] S300: Determine a target collection method according to confirmation information provided by the target supplier and the data connection maturity.

[0088] Specifically, there are various types of supplier docking, among which the types of systems used or purchased by different suppliers are also diverse, including privately deployed systems, SaaS cloud products, local paper documents, etc., so multiple data docking forms are required. This application needs to determine the corresponding target collection method based on the confirmation information of the target supplier and the data docking maturity. For the specific determination of the data collection docking method, please refer to the following embodiments S310, S320 and S330.

[0089] In some embodiments, the step of determining the target collection method according to the confirmation information provided by the target supplier and the data docking maturity includes:

[0090] S310: If the data connection maturity is the first connection maturity, and the confirmation information indicates that the first collection method is selected, determining that the target collection method is the first collection method;

[0091] S320: If the data connection maturity is the second connection maturity, and the confirmation information indicates that the second collection method is selected, determine that the target collection method is the second collection method;

[0092] S330: If the data connection maturity is the third connection maturity, determine that the target collection method is the third collection method.

[0093] Specifically, when the data connection maturity is the first connection maturity, the target supplier may support the first to third situations mentioned above. If it is the second to third situations, if the target supplier provides the chain owner with confirmation information that the first collection method is selected based on security or other considerations, then it can be determined that the target collection method for the chain owner to obtain data from the target supplier is the first collection method. Of course, if the target supplier provides the chain owner with confirmation information that the second collection method is selected based on security or other considerations, then it can be determined that the target collection method for the chain owner to obtain data from the target supplier is the second collection method.

[0094] When the data connection maturity is the second connection maturity, the target supplier may support the fourth to fifth situations mentioned above. If the target supplier provides confirmation information to the chain owner that the second collection method is selected based on security or other considerations, then it can be determined that the target collection method for the chain owner to obtain data from the target supplier is the second collection method.

[0095] When the data connection maturity is the third connection maturity, the target supplier supports the sixth situation mentioned above. If the target supplier provides confirmation information to the chain owner based on security or other considerations that the third collection method is selected, then it can be determined that the target collection method for the chain owner to obtain data from the target supplier is the third collection method.

[0096] S400: Acquire corresponding target data according to the target acquisition method and the target acquisition parameters.

[0097] Specifically, continuing with the above embodiment, after the target data collection method and target collection parameters are passed, the data collection system can obtain the target data from the target supplier according to the target collection parameters through any one or more of the proxy service component 31, the application program interface 50 (API interface) and the message push component 40 (EMQ). For obtaining the corresponding target data, refer to the following embodiments S410, S420 and S430.

[0098] In some embodiments, the step of acquiring corresponding target data according to the target acquisition mode and the target acquisition parameters in S400 includes:

[0099] S410: if the target collection method is the first collection method, establish communication with the proxy service component 31 deployed on the third server 30 used by the target supplier to obtain the target data according to the target collection parameters; or

[0100] S420: if the target acquisition method is the second acquisition method, obtaining the target data from a third-party server rented by the target supplier through the application program interface 50 according to the target acquisition parameters; or

[0101] S430: If the target collection method is the third collection method, establish communication with the message push component 40 deployed on the third server 30 used by the target supplier, search for the target data according to the target collection parameters, and receive the target data sent by the message push component 40.

[0102] Specifically, when the target collection method is the first collection method, that is, the Agent deployment collection method, the supplier system used by the target supplier is a localized system or a localized server (that is, the third server 30), that is, the target supplier stores the above-mentioned supplier-related data on the third server 30 for management. In this way, the agent service component 31 (Agent Manager) can be deployed on the third server 30 used by the target supplier, and the agent service component 31 can collect any data content stored in the third server 30. If the data requirements change with the adjustment of the business, the collection content can be changed on the data collection system. Then, the target data is obtained through the agent service component 31 deployed on the third server 30, and the target data is uploaded to the data collection system.

[0103] Preferably, after the proxy service component 31 collects the target data from the third server 30, it can use an encryption algorithm such as a hash algorithm, an AES algorithm, etc. to encrypt the target data before uploading it to the data collection system. It can also combine the hash algorithm, the AES algorithm, the timestamp, and the private key agreed upon by the chain leader and the target supplier to encrypt the target data before uploading it to the data collection system.

[0104] For example, Figure 2 As shown, the data acquisition system is deployed on a second server 10 that provides data transfer and processing services to a third party. Figure 2 As shown, an agent service component 31 is deployed on the third server 30 (also referred to as the third server 30 in the above embodiment) of the target supplier, and multiple Agent Clients are created through the agent service component 31. One Agent Client corresponds to an independent collection task, and the target data can be collected in parallel through the collection tasks. Figure 2As shown, the Agent Client can be configured and issued in the second server 10.

[0105] When the target collection method is the second collection method, that is, the API interface collection method, the supplier system used by the target supplier is a cloud platform (such as a SaaS platform) or a fourth server that rents a server from a third party for data management, that is, the target supplier has the cloud platform (such as a SaaS platform) or the fourth server for management and storage of the above-mentioned supplier-related data. In this way, the agent service component 31 (Agent Manager) cannot be deployed on the third server 30 used by the target supplier. Therefore, in order to dock the data interface according to the API interface specification of the cloud platform (such as a SaaS platform) or the fourth server, it is necessary to have a developer account and third-party login authorization of the cloud platform (such as a SaaS platform) or the fourth server, and then through the API interface provided by the cloud platform (such as a SaaS platform) or the fourth server, the second server 10 queries and stores the data of the cloud platform (such as a SaaS platform) or the fourth server according to the data requirements of the chain master side. In addition, the data structure, authentication rules of the cloud platform (such as a SaaS platform) or the fourth server and the second server 10 are converted to comply with the data structure and authentication rules of the second server 10. In this way, Figure 3 As shown, when the target supplier is capable of connecting with the second server 10 through the API interface, the target supplier can obtain the target data required by the chain owner from the cloud platform (such as the SaaS platform) or the fourth server, and then the development engineer of the target supplier can actively send the target data to the second server 10 using the API interface provided by the second server 10. Figure 4 As shown, when the target supplier has purchased the API interface service of the cloud platform (such as SaaS platform) or the fourth server, the second server 10 can actively capture and collect target data from the API interface provided by the cloud platform (such as SaaS platform) or the fourth server. Figure 3 Or Figure 4 As shown, the second server 10 can obtain the target data from the target supplier through the API interface from the cloud platform (such as a SaaS platform) or the fourth server.

[0106] When the target collection method is the third collection method, that is, EMQ (Erlang MQTT Broker) collection method, EMQ is an open source message push middleware. The target supplier has neither the third server 30 nor rents a cloud platform (such as a SaaS platform) or a fourth server, or the target supplier believes that the target collection methods through the first collection method and the second collection method have the risk of leakage, therefore, the target collection method that can be selected is the third collection method. In this way, if Figure 5 As shown, the development engineer of the target supplier may digitize the organized target data, and actively push the digitized target data to the second server 10 through the message push component 40 (ie, EMQ).

[0107] Among them, EMQ uses the MQTT protocol, which is a TCP / IP communication protocol. The target supplier has a batch of target data that meets the needs of the chain master. The target supplier obtains the IP address and port number of the second server 10, and uses the second server 10 as a data storage server. The target data is uploaded to the second server 10 in the form of EMQ push.

[0108] In some embodiments, it also includes: S311, if the first database of the third server 30 does not support the proxy service component 31 for data collection, convert the data corresponding to the first database into data corresponding to the second database, and obtain the target data from the second database, and the second database supports the proxy service component 31 for data collection.

[0109] Specifically, in the collection method of the proxy service component 31, if the server of the third party that the chain owner and the supplier of the supply chain trust, that is, the second server 10, cannot support certain types of databases, the data of the unsupported database type is extracted to obtain the corresponding data of the first database, and the corresponding data of the first database is converted into the data type of the currently supported second database before data collection. In other words, for the database type encountered, such as the data in the first database, the current second server 10 cannot directly collect data from the first database, but can convert it, and forward the unsupported first database data to the second database that supports direct collection through a data script, so that data collection can be performed. Of course, program scripts for unsupported database types can also be developed to reduce the number of unsupported first databases, reduce the conversion probability, and improve data collection efficiency.

[0110] Exemplarily, the second server 10 supports data reading and collection directly from the MySQL database, but does not support data reading and collection from the Qraclr database. In this case, a development engineer may write a data extraction script for the Qraclr database, or use a data extraction tool to send the data in the Qraclr database to the MySQL database (there may be operations such as data type conversion in the middle), and establish a synchronization relationship between the two types of databases. The present application may deploy the synchronization script or data extraction tool on the third server 30 of the target supplier or on the second server 10 of a third party according to actual needs.

[0111] In some embodiments, the step of acquiring corresponding target data according to the target acquisition method and the target acquisition parameters includes:

[0112] S500, performing data cleaning processing on the target data, and outputting the cleaned target data;

[0113] S600: Normalize the cleaned target data to obtain target data that complies with a preset data format specified by the chain owner.

[0114] Specifically, due to the variety of production equipment types, there are a large number of different types of data formats. And due to the uneven level of informationization of suppliers, a large amount of noise data will be generated in the process of data collection with suppliers, which needs to be processed, cleaned and handled.

[0115] Data cleaning processing can be performed by first setting up a data cleaning model, and then cleaning the target data collected from different target suppliers through the data cleaning model to output the cleaned target data. Alternatively, the target data collected from different target suppliers can be directly checked for duplicates, and duplicate data can be deleted to output the cleaned target data. Alternatively, the target data collected from different target suppliers can be cleaned according to a preset standard format to filter out redundant information, including missing value cleaning, format content cleaning, and logical error cleaning to output the cleaned target data.

[0116] Because the target data is obtained from different target suppliers, the target data has multi-source heterogeneous characteristics. For example, multi-source heterogeneous panel data may include structured data, semi-structured data, and unstructured data. Structured data refers to data organized according to certain formats and rules. Semi-structured data is a data type between structured data and unstructured data. It has some structured characteristics, but does not fully conform to the format and rules of traditional structured data. Unstructured data is a data type that has no clear structure or cannot be simply explained, such as image data, audio data, video data, and text data. The chain owner sets the target data format that meets its own needs in advance, and renames and converts the cleaned target data according to the target data format to obtain structured target data.

[0117] In some embodiments, the target data is encrypted before transmission.

[0118] Specifically, Figures 2 to 5As shown, after acquiring the target data from the target supplier, the acquired target data can be directly sent to the first server 20. After receiving the target data, the first server 20 cleans and normalizes the target data according to the process of S500-S600. Of course, in order to reduce the development pressure of the chain master tester and the pressure of the first server 20, it is preferred to deploy the data acquisition system in the second server 10. After receiving the target data, the second server 10 cleans and normalizes the target data before forwarding it to the first server 20.

[0119] Specifically, Figure 2 The third server 30 first encrypts the target data and then sends the encrypted target data to the second server 10. The second server 10 cleans and normalizes the target data and then encrypts the processed target data and then sends it to the first server 20. Figure 3 and Figure 4 As shown, after the application program interface 50 obtains the target data, it first encrypts the target data and then sends the encrypted target data to the second server 10. After the second server 10 cleans and normalizes the target data, it encrypts the processed target data and then sends it to the first server 20. Figure 5 As shown, after the message push component 40 obtains the target data, it first encrypts the target data, and then sends the encrypted target data to the second server 10. After the second server 10 cleans and normalizes the target data, it encrypts the processed target data and then sends it to the first server 20. In short, the target data is encrypted before transmission, so that the target data is fully encrypted in the entire transmission link, which improves the security of the target data, prevents illegal elements from tampering with the target data, and protects the interests of both suppliers and chain owners.

[0120] Based on a flexible data collection method, the present application can ensure data upload, processing, calculation, and full-link encryption. The present application can flexibly select the location for the deployment of the data collection system. First, if the supplier side has the ability and resources, the data collection system of the present application can be deployed on the third server 30 on the supplier side according to actual needs, and the supplier's data can be acquired, stored, and processed through the third server 30. Second, the data collection system of the present application can be deployed on the second server 10 provided by a third party, and the supplier's data can be acquired, stored, and processed through the second server 10. Third, considering the need for data security and convenient management, the data collection system of the present application can also be deployed on the first server 20 provided by the chain owner, and the supplier's data can be acquired, stored, and processed through the first server 20.

[0121] This application uses a data system to evaluate the production and operation of a factory, and timely aggregates and integrates production data to obtain relevant indicators. (From the perspective of the chain owner, the data collection of each supplier is uniformly managed. Compared with other data synchronization systems, more perspectives are synchronization between enterprises). This application supports multiple data collection methods, which is convenient for rapid implementation according to actual conditions. (If the supplier does not allow the deployment of Agent collection services in the server, it supports deployment in other service environments to obtain supplier data). This application can achieve full-link encryption during the transmission process of the target data, one end and one cipher, and finally the chain owner decrypts the data.

[0122] This application supports multiple data sources, that is, it supports structured (Mysql, PGSQL, MongoDB...), semi-structured (Excel, CSV, XML...) and unstructured (picture) data extraction to meet the data transmission conditions of different suppliers. This application is transparent and secure, which can connect to various key data generated by suppliers. It is the basis for realizing the digital evaluation of suppliers' production capacity. This application adopts one-end-one-key in the data connection process to ensure data security. This application implements process standardization, that is, under the premise of heterogeneity of data types and data quality, no personalized customization is required. A set of standards is used for data collection configuration, processing and sending. At the same time, the data collection configuration can be flexibly adjusted as the business changes. This application can promote the relationship between suppliers and chain owners, reduce manual entry errors, save business costs, improve supply chain efficiency and reduce labor costs; increase profits for both parties, reduce inventory backlogs, improve business profit margins and promote customer relationships; collection tasks clarify business processes and avoid disputes between the two parties.

[0123] The present application also provides a supply chain data collection system, including:

[0124] An evaluation module, used to evaluate and obtain corresponding data supply maturity according to feedback information provided by a target supplier to a chain owner, and determine data docking maturity according to the feedback information, wherein the target supplier and the chain owner are located in the same supply chain;

[0125] A processing module, used to determine target collection parameters according to the feedback information and the data supply maturity, and determine the target collection method according to the confirmation information provided by the target supplier and the data connection maturity;

[0126] The acquisition module is used to acquire corresponding target data according to the target acquisition method and the target acquisition parameters.

[0127] In specific implementation, the above units or modules can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The above units or modules can refer to the previous method embodiments to implement data collection for supply chain management projects, which will not be repeated here.

[0128] Those skilled in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions, or by controlling related hardware through instructions, and the instructions can be stored in a computer-readable storage medium, and loaded and executed by a processor to implement the above method embodiments. The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0129] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, reference can be made to the relevant description of other embodiments. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process and beneficial effects of the data acquisition system and its corresponding units described above can refer to the description of the supply chain data collection method in the above embodiment, and will not be repeated here.

[0130] The above is a detailed introduction to a supply chain data collection method and system provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for collecting supply chain data, characterized in that: Includes steps: The corresponding data supply maturity is evaluated according to the feedback information provided by the target supplier to the chain owner, and the data connection maturity is determined according to the feedback information, wherein the target supplier and the chain owner are located in the same supply chain; the feedback information includes the data to be provided that the target supplier allows to be provided to the chain owner, and the data collection method that the target supplier supports the chain owner to collect data; The step of evaluating and obtaining the corresponding data supply maturity according to the feedback information provided by the target supplier to the chain owner includes: Obtaining, according to the data to be provided, the data type and number of types of data that the target supplier is allowed to provide to the chain owner; Determining the data supply maturity according to the data type and the number of types; The step of determining the data connection maturity according to the feedback information comprises: If the data collection method includes at least the first collection method, determining the data docking maturity to be the first docking maturity; If the data collection method includes at least the second collection method and does not support the first collection method, determining the data connection maturity to be the second connection maturity; If the data collection method is the third collection method, determining the data connection maturity to be the third connection maturity; Wherein, the first docking maturity is greater than the second docking maturity, and the second docking maturity is greater than the third docking maturity; Determine target acquisition parameters according to the feedback information and the data supply maturity; the target acquisition parameters include index fields, and the index fields are key fields corresponding to different types of data to be provided; Determine the target collection method according to the confirmation information provided by the target supplier and the data connection maturity; the target collection method includes any one of the first collection method, the second collection method and the third collection method, the first collection method is the proxy service component deployment collection method, the second collection method is the application program interface collection method, and the third collection method is the message push component collection method; The corresponding target data is acquired according to the target acquisition mode and the target acquisition parameters.

2. The method for collecting supply chain data according to claim 1, characterized in that: The step of determining the data supply maturity according to the data type and the number of types includes: According to the data type, a preset relationship table is queried to obtain a data importance level corresponding to the data type, and a first maturity parameter is determined according to the data importance level corresponding to the data type; the preset relationship table includes a corresponding relationship between the data type and the data importance level, and the first maturity parameter is positively correlated with the data importance level; determining a second maturity parameter according to the number of species, wherein the second maturity parameter is positively correlated with the number of species; The corresponding data supply maturity is obtained by performing weighted calculation according to the first maturity parameter and the second maturity parameter.

3. The method for collecting supply chain data according to claim 2, characterized in that: The step of determining target acquisition parameters according to the feedback information and the data supply maturity comprises: According to the feedback information and the data supply maturity, set corresponding index fields and data collection strategies, wherein the data collection strategies include collection frequency and number of retries for collection failure; According to the feedback information and the input information provided by the target supplier, a corresponding collection scope is set; Wherein, the target acquisition parameters also include at least one of the data acquisition strategy and the acquisition range.

4. The method for collecting supply chain data according to claim 1, characterized in that: The step of determining the target collection method according to the confirmation information provided by the target supplier and the data docking maturity includes: If the data connection maturity is the first connection maturity, and the confirmation information indicates that the first collection method is selected, determining that the target collection method is the first collection method; If the data connection maturity is the second connection maturity, and the confirmation information indicates that the second collection method is selected, determining that the target collection method is the second collection method; If the data connection maturity is the third connection maturity, and the confirmation information is that the third collection method is selected, the target collection method is determined to be the third collection method.

5. The method for collecting supply chain data according to claim 4, characterized in that: The step of acquiring corresponding target data according to the target acquisition mode and the target acquisition parameters comprises: If the target collection method is the first collection method, establish communication with an agent service component deployed on a third server used by the target supplier to obtain the target data according to the target collection parameters; or, If the target acquisition method is the second acquisition method, obtaining the target data from a third-party server rented by the target supplier according to the target acquisition parameters through an application program interface; or, If the target collection method is the third collection method, establish communication with the message push component deployed on the third server used by the target supplier, search for the target data according to the target collection parameters, and receive the target data sent by the message push component.

6. The method for collecting supply chain data according to claim 5, characterized in that: The step of establishing communication with the proxy service component deployed on the third server used by the target supplier to obtain the target data according to the target collection parameters comprises the following steps: If the first database of the third server does not support the proxy service component for data collection, the data corresponding to the first database is converted into data corresponding to a second database, and the target data is obtained from the second database, and the second database supports the proxy service component for data collection.

7. The method for collecting supply chain data according to any one of claims 1 to 6, characterized in that: The step of obtaining the corresponding target data according to the target acquisition method and the target acquisition parameters includes: Performing data cleaning on the target data and outputting the cleaned target data; The cleaned target data is normalized to obtain target data that conforms to a preset data format specified by the chain owner.

8. A supply chain data collection system, characterized in that: include: An evaluation module, used to evaluate and obtain the corresponding data supply maturity according to the feedback information provided by the target supplier to the chain owner, and determine the data docking maturity according to the feedback information, wherein the target supplier and the chain owner are located in the same supply chain; the feedback information includes the data to be provided that the target supplier allows to be provided to the chain owner, and the data collection method that the target supplier supports the chain owner to collect data; The corresponding data supply maturity obtained by evaluating the feedback information provided by the target supplier to the chain owner includes: Obtaining, according to the data to be provided, the data type and number of types of data that the target supplier is allowed to provide to the chain owner; Determining the data supply maturity according to the data type and the number of types; Determining the data connection maturity according to the feedback information includes: If the data collection method includes at least the first collection method, determining the data docking maturity to be the first docking maturity; If the data collection method includes at least the second collection method and does not support the first collection method, determining the data connection maturity to be the second connection maturity; If the data collection method is the third collection method, determining the data connection maturity to be the third connection maturity; Wherein, the first docking maturity is greater than the second docking maturity, and the second docking maturity is greater than the third docking maturity; A processing module, used to determine target collection parameters according to the feedback information and the data supply maturity, and determine the target collection method according to the confirmation information provided by the target supplier and the data connection maturity; the target collection parameters include index fields, which are key fields corresponding to different types of data to be provided; A collection module is used to obtain corresponding target data according to the target collection method and the target collection parameters; the target collection method includes any one of a first collection method, a second collection method and a third collection method, the first collection method is a proxy service component deployment collection method, the second collection method is an application program interface collection method, and the third collection method is a message push component collection method.

Images