Cross-platform shared component design change implementation management and control method, system, device and storage medium

Abstract

The present application relates to a method, system, device and storage medium for implementing and controlling design changes of cross-platform common parts, and relates to the field of product data management, including constructing a cross-platform part code database that includes a first mapping relationship between the main part code and the sub-part code of the cross-platform common parts, and a second mapping relationship between the sub-part code and the vehicle model code; when a design change including a target sub-part code corresponding to a target cross-platform common part initiated by a target sub-platform is received, based on the first mapping relationship, the target main part code corresponding to the target sub-part code is located from the cross-platform part code database; based on the target main part code, the sub-part codes of other sub-platforms corresponding to it are located from the cross-platform part code database; based on the second mapping relationship, the target vehicle model code corresponding to the sub-part codes of other sub-platforms is located from the cross-platform part code database, so as to accurately and quickly locate the vehicle model using the cross-platform common parts.

Description

Technical Field

[0001] The present application relates to the technical field of product data management, and in particular to a method, system, device and storage medium for implementing and managing cross-platform shared component design changes. Background Art

[0002] At present, in order to cope with the fierce competition in the automobile market in recent years, a large number of design changes to parts are often required during the process of automobile development, production and manufacturing. Among them, there are not only common parts (i.e. parts or assemblies used by multiple different models at the same time and with the same part coding) in automobile parts, but these common parts may also be cross-platform common parts (i.e. parts or assemblies used by multiple companies at the same time and with inconsistent part coding under the group system). Once a cross-platform common part undergoes a design change, it will affect all models on all platforms that use the cross-platform common part. At this time, it is necessary to accurately and quickly realize the positioning of the models related to the cross-platform common parts to ensure the unified implementation of collaborative design changes. However, at present, only the positioning of the models using common parts under a single platform has been achieved, and the positioning of the models using cross-platform common parts cannot be achieved. Summary of the Invention

[0003] The present application provides a method, system, device and storage medium for implementing and managing the design changes of cross-platform shared parts to solve the problem in related technologies that it is impossible to accurately and quickly locate the vehicle models using cross-platform shared parts.

[0004] In a first aspect, a method for implementing and managing cross-platform shared component design changes is provided. The method is applied to a main platform and includes the following steps:

[0005] Building a cross-platform part code database, the cross-platform part code database including a first mapping relationship between a main part code and a sub-part code of a cross-platform common part, and a second mapping relationship between a sub-part code and a vehicle model code, wherein the main part code is the part code of the cross-platform common part on the main platform, and the sub-part code is the part code of the cross-platform common part on the sub-platform;

[0006] When receiving a design change including a target sub-part code corresponding to a target cross-platform common component initiated by a target sub-platform, locating a target main part code corresponding to the target sub-part code from the cross-platform part code database based on the first mapping relationship;

[0007] Locating, based on the target main part code, the sub-part codes of other sub-platforms corresponding thereto from the cross-platform part code database;

[0008] Based on the second mapping relationship, a target vehicle model code corresponding to the sub-part code of another sub-platform is located from the cross-platform part code database.

[0009] In some embodiments, after the step of locating the target vehicle model code corresponding to the sub-part code of another sub-platform from the cross-platform part code database based on the second mapping relationship, the method further includes:

[0010] Send the design changes and target vehicle model codes corresponding to the target cross-platform common parts to the corresponding other sub-platforms, so that the other sub-platforms can determine the target design change implementation nodes corresponding to the target cross-platform common parts based on the design changes and target vehicle model codes;

[0011] Based on the target design change implementation nodes of other sub-platforms and the design change implementation nodes of the target cross-platform common components on the target sub-platform, the main control platform and the secondary control platform are determined from the other sub-platforms and the target sub-platform.

[0012] In some embodiments, after determining the primary control platform and the secondary control platform, the following steps are further included:

[0013] Obtaining the production preparation tasks corresponding to the target cross-platform common parts created by the primary control platform based on the design changes and the design change implementation nodes, and transmitting the production preparation tasks to the secondary control platform;

[0014] Obtaining secondary control confirmation information sent by the secondary control platform based on the production preparation task;

[0015] The secondary control confirmation information is transmitted to the main control platform so that the main control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself.

[0016] In some embodiments, the primary control platform controls the trial assembly verification, inventory quantity, and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the primary control confirmation information corresponding to the production preparation task collected by the primary control platform itself, including:

[0017] The main control platform constructs a supplier confirmation item based on the main control confirmation information and the secondary control confirmation information, and transmits the supplier confirmation item to the supplier;

[0018] The main control platform obtains supply information corresponding to the target cross-platform common part transmitted by the supplier based on the supplier confirmation item, wherein the supply information includes a mold repair cycle and a delivery time of the target cross-platform common part;

[0019] The main control platform builds a production preparation plan according to the supply information, and controls the trial assembly verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

[0020] In some embodiments, after the main control platform constructs a production preparation plan based on the supply information, the method further includes:

[0021] Obtain the production preparation plan delivered by the main control platform, and deliver the production preparation plan to the secondary control platform so that the secondary control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

[0022] In a second aspect, a cross-platform shared component design change implementation management and control system is provided, the system including a main platform, the main platform being used to:

[0023] Building a cross-platform part code database, the cross-platform part code database including a first mapping relationship between a main part code and a sub-part code of a cross-platform common part, and a second mapping relationship between a sub-part code and a vehicle model code, wherein the main part code is the part code of the cross-platform common part on the main platform, and the sub-part code is the part code of the cross-platform common part on the sub-platform;

[0024] When receiving a design change including a target sub-part code corresponding to a target cross-platform common component initiated by a target sub-platform, locating a target main part code corresponding to the target sub-part code from the cross-platform part code database based on the first mapping relationship;

[0025] Locating, based on the target main part code, the sub-part codes of other sub-platforms corresponding thereto from the cross-platform part code database;

[0026] Based on the second mapping relationship, a target vehicle model code corresponding to the sub-part code of another sub-platform is located from the cross-platform part code database.

[0027] In some embodiments, the main platform is further used to:

[0028] Send the design changes and target vehicle model codes corresponding to the target cross-platform common parts to the corresponding other sub-platforms, so that the other sub-platforms can determine the target design change implementation nodes corresponding to the target cross-platform common parts based on the design changes and target vehicle model codes;

[0029] Based on the target design change implementation nodes of other sub-platforms and the design change implementation nodes of the target cross-platform common components on the target sub-platform, the main control platform and the secondary control platform are determined from the other sub-platforms and the target sub-platform.

[0030] In some embodiments, the main platform is further used to:

[0031] Obtaining the production preparation tasks corresponding to the target cross-platform common parts created by the primary control platform based on the design changes and the design change implementation nodes, and transmitting the production preparation tasks to the secondary control platform;

[0032] Obtaining secondary control confirmation information sent by the secondary control platform based on the production preparation task;

[0033] The secondary control confirmation information is transmitted to the main control platform so that the main control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself.

[0034] In a third aspect, a cross-platform shared component design change implementation and management device is provided, comprising: a memory and a processor, wherein the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the aforementioned cross-platform shared component design change implementation and management method.

[0035] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the aforementioned cross-platform shared component design change implementation and management method is implemented.

[0036] The present application provides a method, system, device and storage medium for implementing and controlling design changes of cross-platform common parts, including constructing a cross-platform part coding database, wherein the cross-platform part coding database includes a first mapping relationship between the main part code and the sub-part code of the cross-platform common part and a second mapping relationship between the sub-part code and the vehicle model code, wherein the main part code is the part code of the cross-platform common part on the main platform, and the sub-part code is the part code of the cross-platform common part on the sub-platform; when a design change including a target sub-part code corresponding to a target cross-platform common part initiated by a target sub-platform is received, based on the first mapping relationship, the target main part code corresponding to the target sub-part code is located from the cross-platform part coding database; based on the target main part code, the sub-part codes of other sub-platforms corresponding thereto are located from the cross-platform part coding database; based on the second mapping relationship, the target vehicle model code corresponding to the sub-part codes of other sub-platforms is located from the cross-platform part coding database. Through the present application, the vehicle models used for cross-platform common parts can be accurately and quickly located to ensure the unified implementation of collaborative design changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0038] Figure 1 A flowchart of a method for implementing and managing cross-platform shared component design changes provided in an embodiment of the present application;

[0039] Figure 2 A schematic diagram of the mapping relationship in the cross-platform part coding database provided in an embodiment of the present application;

[0040] Figure 3 A schematic diagram of positioning part coding and vehicle model code based on design changes provided in an embodiment of the present application;

[0041] Figure 4 A schematic diagram of the structure of a cross-platform shared component design and implementation control device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0043] For the convenience of description, the relevant professional terms appearing in the specific implementation methods are first explained:

[0044] Common parts: refers to parts or assemblies that are used by two or more projects at the same time and have the same part number.

[0045] Cross-platform shared parts: refers to parts or assemblies that are used by multiple companies or platforms at the same time within the group system and have inconsistent part numbers.

[0046] Design changes: Part changes due to process improvements, quality improvements, cost reductions, demand changes, etc.

[0047] Implementation of import: After the design change of the part is initiated, the part is controlled to be loaded and verified in a certain state according to the production preparation time of procurement, manufacturing process and manufacturing management.

[0048] The embodiments of the present application provide a method, system, device and storage medium for implementing and managing the design changes of cross-platform shared parts, which can solve the problem in related technologies that it is impossible to accurately and quickly locate the vehicle model using cross-platform shared parts.

[0049] Figure 1 The present invention provides a method for implementing and managing cross-platform shared component design changes. The method is applied to the main platform and includes the following steps:

[0050] Step S10: Constructing a cross-platform part code database, wherein the cross-platform part code database includes a first mapping relationship between a main part code and a sub-part code of a cross-platform common part, and a second mapping relationship between a sub-part code and a vehicle model code. The main part code is the part code of the cross-platform common part on the main platform, and the sub-part code is the part code of the cross-platform common part on the sub-platform.

[0051] For example, it is understandable that vehicle development usually requires the collaborative work of multiple units, and the parts coding standards and specifications of each unit are often different. Therefore, the part coding of the same cross-platform common parts on different platforms is also different. Therefore, when the cross-platform common parts undergo design changes, it is necessary to accurately and quickly locate the vehicle models related to the cross-platform common parts to ensure the unified implementation of the collaborative design changes.

[0052] In this embodiment, a cross-platform part code database is established on the main platform based on the design system. Cross-platform shared components are assigned unique part codes on the main platform, namely, primary part codes. It should be understood that cross-platform shared components also have unique part codes on each cooperating sub-platform, namely, sub-part codes. All vehicle models within a sub-platform that use the cross-platform shared component have corresponding sub-part codes. Therefore, this embodiment creates a first mapping relationship between primary part codes and sub-part codes, and a second mapping relationship between sub-part codes and vehicle model codes, in the cross-platform part code database.

[0053] For example, for a cross-platform shared part a, its main part code on the main platform is X2000000, its sub-part code on the sub-platform A is A10000000 and the models that use the cross-platform shared part a include A1, its sub-part code on the sub-platform B is B3000000000 and the models that use the cross-platform shared part a include B1, B2 and B3, its sub-part code on the sub-platform C is C4000 and the models that use the cross-platform shared part a include C1, C2 and C3, its sub-part code on the sub-platform D is D50000000 and the models that use the cross-platform shared part a include D1 and D2, then it can be constructed Figure 2 The mapping relationship shown.

[0054] Step S20: When a design change including a target sub-part code corresponding to a target cross-platform common component is received and initiated by the target sub-platform, a target main part code corresponding to the target sub-part code is located from the cross-platform part code database based on the first mapping relationship;

[0055] For example, in this embodiment, see Figure 3 As shown in the figure, when a design change is required for a cross-platform shared part (also known as the target cross-platform shared part) in a sub-platform (also known as the target sub-platform, such as sub-platform A), the designer will initiate a design change for the target cross-platform shared part (for example, the sub-part code of the target cross-platform shared part on sub-platform A is A10000000) based on the design change application and transmit the design change to the main platform. It should be noted that due to the inconsistency of the platform coding systems of different companies, the part codes of the target cross-platform shared part on other sub-platforms are different, that is, there are multiple part codes. Therefore, when the main platform receives the design change initiated by sub-platform A for the target cross-platform shared part A10000000, it will search the cross-platform part coding database by code to locate the main part code corresponding to A100000000: X2000000.

[0056] Step S30: locating the corresponding sub-part codes of other sub-platforms from the cross-platform part code database based on the target main part code;

[0057] For example, see Figure 3 As shown, after obtaining the main part code X2000000 of the target cross-platform common part, the main part code X2000000 will be used to retrieve and locate the collaborative sub-platforms B, C and D that use the target cross-platform common part from the cross-platform part code database, and obtain the corresponding sub-part codes B3000000000, C4000 and D50000000.

[0058] Step S40: Locate the target vehicle model code corresponding to the sub-part code of other sub-platforms from the cross-platform part code database based on the second mapping relationship.

[0059] For example, see Figure 3As shown, after locating the sub-part codes B3000000000, C4000 and D50000000 respectively corresponding to sub-platforms B, C and D, the vehicle model codes using the target cross-platform common parts in each sub-platform can be retrieved and located from the cross-platform part coding database through the sub-part codes B3000000000, C4000 and D50000000, that is, B1, B2, B3 corresponding to B3000000000, C1, C2, C3 corresponding to B300000000, and D1 and D2 corresponding to D500000000. Therefore, for the design change of the target cross-platform common part with the sub-part code A10000000, the collaborative sub-platforms involved include B, C and D and the vehicle models involved include B1, B2, B3, C1, C2, C3, D1 and D2.

[0060] As can be seen, in this embodiment, when a design change is initiated for a cross-platform shared part, the different part codes under different platforms can be quickly identified and the vehicle model used for the cross-platform shared part can be located. In summary, in the context of collaborative work, this embodiment establishes a cross-platform part code database to achieve rapid, linked retrieval of shared parts based on the platform coding system of each platform and vehicle model, thereby accurately and quickly locating the platform and vehicle model corresponding to the cross-platform shared part.

[0061] Furthermore, after the step of locating the target vehicle model code corresponding to the sub-part code of another sub-platform from the cross-platform part code database based on the second mapping relationship, the method further includes:

[0062] Send the design changes and target vehicle model codes corresponding to the target cross-platform common parts to the corresponding other sub-platforms, so that the other sub-platforms can determine the target design change implementation nodes corresponding to the target cross-platform common parts based on the design changes and target vehicle model codes;

[0063] Based on the target design change implementation nodes of other sub-platforms and the design change implementation nodes of the target cross-platform common components on the target sub-platform, the main control platform and the secondary control platform are determined from the other sub-platforms and the target sub-platform.

[0064] For example, in this embodiment, after the master platform identifies and locates all cooperating sub-platforms and their vehicle model codes corresponding to the target cross-platform common component, it will transmit the design changes related to the target cross-platform common component to other related sub-platforms. For example, the master platform transmits the design changes of the target cross-platform common component and vehicle model information including B1, B2, and B3 to sub-platform B, and transmits the design changes of the target cross-platform common component and vehicle model information including C1, C2, and C3 to sub-platform C. This allows sub-platforms B, C, and D to determine the target design change implementation node of the target cross-platform common component on their own platforms based on the received design changes and vehicle model information.

[0065] Among them, the target design change implementation node can be determined according to the order of implementation time of different models. For example, taking the implementation node of the target cross-platform shared parts on sub-platform B as an example, the implementation time of model B1 is August 25, the implementation time of model B2 is June 20, and the implementation time of model B3 is July 13. The order of implementation time of B1 to B3 is B2>B3>B1, and the implementation time of B2 is used as the target design change implementation node, that is, the target design change implementation node is June 20. Similarly, the target sub-platform (that is, sub-platform A) also needs to determine the design change implementation node corresponding to the target cross-platform shared parts according to the above method.

[0066] After all sub-platforms have determined their own design change implementation nodes, the main control platform and the secondary control platform are determined from all sub-platforms using the target cross-platform shared components according to the order of the design change implementation nodes of all sub-platforms, so as to distinguish the main control platform and the secondary control platform.

[0067] For example, the design change implementation nodes of sub-platforms A, B, C, and D are a1, b1, c1, and d1 respectively. If:

[0068] If a1>b1\c1\d1, then sub-platform A is determined to be the primary control platform and its person in charge of design and change control is the primary control person, and sub-platforms B, C, and D are determined to be secondary control platforms and their persons in charge of design and change control are secondary control persons;

[0069] If b1>a1\c1\d1, then sub-platform B is determined to be the primary control platform and its person in charge of design and change control is the primary control person, while sub-platforms A, C, and D are determined to be secondary control platforms and their persons in charge of design and change control are secondary control persons;

[0070] If c1>a1\b1\d1, then sub-platform C is determined to be the primary control platform and its person in charge of design and change control is the primary control person, while sub-platforms A, B, and D are determined to be secondary control platforms and their persons in charge of design and change control are secondary control persons;

[0071] If d1>a1\b1\c1, then sub-platform D is determined to be the primary control platform and its change control person in charge is the primary control person, and sub-platforms A, B and C are determined to be secondary control platforms and their change control persons in charge are secondary control persons.

[0072] Furthermore, after determining the primary control platform and the secondary control platform, the following steps are also included:

[0073] Obtaining the production preparation tasks corresponding to the target cross-platform common parts created by the primary control platform based on the design changes and the design change implementation nodes, and transmitting the production preparation tasks to the secondary control platform;

[0074] Obtaining secondary control confirmation information sent by the secondary control platform based on the production preparation task;

[0075] The secondary control confirmation information is transmitted to the main control platform so that the main control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself.

[0076] For example, it is understandable that in the context of the collaborative design, manufacturing, and production system of automobiles, vehicle development usually requires the collaborative work of multiple units. Since the standards and specifications for component coding of each unit are different, once a design change occurs for a cross-platform common part, it will lead to problems such as discontinuous workflow and loose process connection when implementing the component design change, resulting in inconsistent implementation progress of cross-platform common parts. In serious cases, it will lead to chaotic supply status, which may cause serious consequences such as delays in project plans or production abnormalities for multiple models on multiple platforms.

[0077] In this embodiment, the main control personnel will create a production preparation task in the main control platform based on the design changes and design change implementation nodes of the target cross-platform shared parts, and send the production preparation task to the corresponding procurement, process, quality and manufacturing parties of the main control platform to collect, summarize and confirm information such as production preparation cycle, inventory quantity, sample delivery time and quantity, trial installation time, and production time to obtain the main control confirmation information; at the same time, the production preparation task will be passed to the main platform, and the main platform will distribute the production preparation task to all sub-control platforms.

[0078] The sub-control personnel will complete the production preparation cycle, inventory quantity, sample delivery time and quantity, trial installation time, and production start time according to the production preparation tasks received from the sub-control platform, obtain sub-control confirmation information, and return it to the main platform through the sub-control platform; then return it to the main control platform through the main platform, so that the main control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform common parts based on the sub-control confirmation information and the main control confirmation information and based on the manufacturing system, thereby realizing the unified management of the implementation control progress of cross-platform common parts design changes in the context of collaborative work, so as to avoid the adverse effects caused by inconsistent implementation import progress of cross-platform common parts, thereby ensuring the orderly progress of collaborative production.

[0079] Furthermore, the main control platform controls the trial assembly verification, inventory quantity, and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself, including:

[0080] The main control platform constructs a supplier confirmation item based on the main control confirmation information and the secondary control confirmation information, and transmits the supplier confirmation item to the supplier;

[0081] The main control platform obtains supply information corresponding to the target cross-platform common part transmitted by the supplier based on the supplier confirmation item, wherein the supply information includes a mold repair cycle and a delivery time of the target cross-platform common part;

[0082] The main control platform builds a production preparation plan according to the supply information, and controls the trial assembly verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

[0083] For example, it can be understood that after the main control platform and the secondary control platform complete the information aggregation of the production preparation tasks, the main control personnel will take the lead in completing the production preparation process tracking. That is, through the main control platform and based on the main control confirmation information and the secondary control confirmation information, the supplier confirmation items including the part mold repair order or mold opening order, the part inventory quantity, the part delivery time, etc. are determined, and the supplier confirmation items are issued to the supplier. The supplier will confirm each supplier confirmation item based on its own operating conditions to obtain supply information including the mold repair cycle and arrival time of the target cross-platform shared parts, and transmit this supply information to the main control platform. After receiving the supply information, the main control platform will construct a production preparation plan based on the supply information, so that the main control personnel can control the trial assembly verification, inventory quantity and switching time corresponding to the target cross-platform shared parts according to the production preparation plan, and at the same time transmit the production preparation plan to the main platform.

[0084] Furthermore, after the step of the main control platform constructing a production preparation plan according to the supply information, the method further includes:

[0085] Obtain the production preparation plan delivered by the main control platform, and deliver the production preparation plan to the secondary control platform so that the secondary control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

[0086] For example, in this embodiment, when the main platform receives the production preparation plan through the main control platform, it will pass the production preparation plan to the sub-control platform, so that the sub-control personnel can cooperate with the production preparation plan received by the sub-control platform to complete the trial installation verification tracking, switching time control, etc. related to the target cross-platform shared parts, and then complete the trial installation verification control, inventory quantity control and switching time control.

[0087] In summary, this embodiment, by establishing a cross-platform parts coding database, not only achieves accurate and rapid positioning and identification of cross-platform shared parts used in different coding systems, but also realizes information sharing between different platforms, providing necessary support for the realization of centralized procurement and other needs, but also can achieve standardized management and design change traceability, effectively improving work efficiency. It can be seen that the cross-platform shared parts design change implementation control method provided by this embodiment realizes the full process control of cross-platform shared parts initiating design changes, locating vehicle models, process control, and production switching, solving the problems of difficulty in introducing cross-platform shared parts design change implementation, high complexity, and inconsistent information.

[0088] It should be noted that the step numbers of the steps in the embodiments of the present application do not limit the order of the operations in the technical solution of the present application.

[0089] The present application also provides a cross-platform shared component design change implementation management and control system, the system including a main platform, the main platform is used to:

[0090] Building a cross-platform part code database, the cross-platform part code database including a first mapping relationship between a main part code and a sub-part code of a cross-platform common part, and a second mapping relationship between a sub-part code and a vehicle model code, wherein the main part code is the part code of the cross-platform common part on the main platform, and the sub-part code is the part code of the cross-platform common part on the sub-platform;

[0091] When receiving a design change including a target sub-part code corresponding to a target cross-platform common component initiated by a target sub-platform, locating a target main part code corresponding to the target sub-part code from the cross-platform part code database based on the first mapping relationship;

[0092] Locating, based on the target main part code, the sub-part codes of other sub-platforms corresponding thereto from the cross-platform part code database;

[0093] Based on the second mapping relationship, a target vehicle model code corresponding to the sub-part code of another sub-platform is located from the cross-platform part code database.

[0094] Furthermore, the main platform is also used for:

[0095] Send the design changes and target vehicle model codes corresponding to the target cross-platform common parts to the corresponding other sub-platforms, so that the other sub-platforms can determine the target design change implementation nodes corresponding to the target cross-platform common parts based on the design changes and target vehicle model codes;

[0096] Based on the target design change implementation nodes of other sub-platforms and the design change implementation nodes of the target cross-platform common components on the target sub-platform, the main control platform and the secondary control platform are determined from the other sub-platforms and the target sub-platform.

[0097] Furthermore, the main platform is also used for:

[0098] Obtaining the production preparation tasks corresponding to the target cross-platform common parts created by the primary control platform based on the design changes and the design change implementation nodes, and transmitting the production preparation tasks to the secondary control platform;

[0099] Obtaining secondary control confirmation information sent by the secondary control platform based on the production preparation task;

[0100] The secondary control confirmation information is transmitted to the main control platform so that the main control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself.

[0101] Furthermore, the main control platform is specifically used to:

[0102] The main control platform constructs a supplier confirmation item based on the main control confirmation information and the secondary control confirmation information, and transmits the supplier confirmation item to the supplier;

[0103] The main control platform obtains supply information corresponding to the target cross-platform common part transmitted by the supplier based on the supplier confirmation item, wherein the supply information includes a mold repair cycle and a delivery time of the target cross-platform common part;

[0104] The main control platform builds a production preparation plan according to the supply information, and controls the trial assembly verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

[0105] Furthermore, the main platform is also used for:

[0106] Obtain the production preparation plan delivered by the main control platform, and deliver the production preparation plan to the secondary control platform so that the secondary control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

[0107] It should be noted that technical personnel in the relevant field can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems and platforms described above can refer to the corresponding processes in the aforementioned cross-platform shared component design and implementation management method embodiment, and will not be repeated here.

[0108] The cross-platform shared component design change implementation management and control system provided in the above embodiment can be implemented in the form of a computer program. The computer program can be used in Figure 4 The cross-platform shared components shown are designed to run on the control device.

[0109] An embodiment of the present application also provides a cross-platform shared component design change implementation and management device, including: a memory, a processor and a network interface connected via a system bus, at least one instruction stored in the memory, and at least one instruction loaded and executed by the processor to implement all or part of the steps of the aforementioned cross-platform shared component design change implementation and management method.

[0110] Among them, the network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0111] The processor may be a CPU, other general-purpose processors, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor, or any conventional processor. The processor is the control center of a computer device, connecting various parts of the entire computer device using various interfaces and lines.

[0112] The memory can be used to store computer programs and / or modules. The processor implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory, and accessing the data stored in the memory. The memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, at least one application required for the function, etc.; the data storage area can store data created based on the use of the system, etc. In addition, the memory can include high-speed random access memory and non-volatile memory, such as a hard disk, internal memory, a plug-in hard disk, an SMC (Smart Media Card), an SD (Secure Digital) card, a flash card, at least one disk storage device, a flash memory device, or other volatile solid-state storage device.

[0113] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, all or part of the steps of the aforementioned cross-platform shared component design change implementation and management method are implemented.

[0114] The embodiments of the present application implement all or part of the aforementioned processes, and may also be completed by instructing the relevant hardware through a computer program. The computer program may be stored in a computer-readable storage medium, and when the computer program is executed by the processor, the steps of each of the above methods may be implemented. Among them, the computer program includes computer program code, and the computer program code may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, ROM (Read-Only memory), RAM (Random Access memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0115] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, servers, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0116] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.

[0117] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0118] The foregoing is merely a list of specific embodiments of the present application, intended to enable those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the broadest scope consistent with the principles and novel features of the present application.

Claims

1. A cross-platform shared component design change implementation management and control method, characterized in that: The method is applied to the main platform and comprises the following steps: Building a cross-platform part code database, the cross-platform part code database including a first mapping relationship between a main part code and a sub-part code of a cross-platform common part, and a second mapping relationship between a sub-part code and a vehicle model code, wherein the main part code is the part code of the cross-platform common part on the main platform, and the sub-part code is the part code of the cross-platform common part on the sub-platform; When receiving a design change including a target sub-part code corresponding to a target cross-platform common component initiated by a target sub-platform, locating a target main part code corresponding to the target sub-part code from the cross-platform part code database based on the first mapping relationship; Locating, based on the target main part code, the sub-part codes of other sub-platforms corresponding thereto from the cross-platform part code database; Based on the second mapping relationship, a target vehicle model code corresponding to the sub-part code of another sub-platform is located from the cross-platform part code database.

2. The cross-platform shared component design change implementation management and control method according to claim 1, characterized in that: After the step of locating the target vehicle model code corresponding to the sub-part code of another sub-platform from the cross-platform part code database based on the second mapping relationship, the method further includes: Send the design changes and target vehicle model codes corresponding to the target cross-platform common parts to the corresponding other sub-platforms, so that the other sub-platforms can determine the target design change implementation nodes corresponding to the target cross-platform common parts based on the design changes and target vehicle model codes; Based on the target design change implementation nodes of other sub-platforms and the design change implementation nodes of the target cross-platform common components on the target sub-platform, the main control platform and the secondary control platform are determined from the other sub-platforms and the target sub-platform.

3. The cross-platform shared component design change implementation management and control method according to claim 2, characterized in that: After determining the steps for the primary and secondary control platforms, the following steps are also included: Obtaining the production preparation tasks corresponding to the target cross-platform common parts created by the primary control platform based on the design changes and the design change implementation nodes, and transmitting the production preparation tasks to the secondary control platform; Obtaining secondary control confirmation information sent by the secondary control platform based on the production preparation task; The secondary control confirmation information is transmitted to the main control platform so that the main control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself.

4. The cross-platform shared component design change implementation management and control method according to claim 3, characterized in that: The main control platform controls the trial assembly verification, inventory quantity, and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself, including: The main control platform constructs a supplier confirmation item based on the main control confirmation information and the secondary control confirmation information, and transmits the supplier confirmation item to the supplier; The main control platform obtains supply information corresponding to the target cross-platform common part transmitted by the supplier based on the supplier confirmation item, wherein the supply information includes a mold repair cycle and a delivery time of the target cross-platform common part; The main control platform builds a production preparation plan according to the supply information, and controls the trial assembly verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

5. The cross-platform shared component design change implementation management and control method according to claim 4, characterized in that: After the main control platform constructs a production preparation plan according to the supply information, the method further includes: Obtain the production preparation plan delivered by the main control platform, and deliver the production preparation plan to the secondary control platform so that the secondary control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the production preparation plan.

6. A cross-platform shared component design change implementation management and control system, characterized by: The system includes a main platform, which is used to: Building a cross-platform part code database, the cross-platform part code database including a first mapping relationship between a main part code and a sub-part code of a cross-platform common part, and a second mapping relationship between a sub-part code and a vehicle model code, wherein the main part code is the part code of the cross-platform common part on the main platform, and the sub-part code is the part code of the cross-platform common part on the sub-platform; When receiving a design change including a target sub-part code corresponding to a target cross-platform common component initiated by a target sub-platform, locating a target main part code corresponding to the target sub-part code from the cross-platform part code database based on the first mapping relationship; Locating, based on the target main part code, the sub-part codes of other sub-platforms corresponding thereto from the cross-platform part code database; Based on the second mapping relationship, a target vehicle model code corresponding to the sub-part code of another sub-platform is located from the cross-platform part code database.

7. The cross-platform shared component design change implementation management and control system according to claim 6, characterized in that: The main platform is also used to: Send the design changes and target vehicle model codes corresponding to the target cross-platform common parts to the corresponding other sub-platforms, so that the other sub-platforms can determine the target design change implementation nodes corresponding to the target cross-platform common parts based on the design changes and target vehicle model codes; Based on the target design change implementation nodes of other sub-platforms and the design change implementation nodes of the target cross-platform common components on the target sub-platform, the main control platform and the secondary control platform are determined from the other sub-platforms and the target sub-platform.

8. The cross-platform shared component design change implementation management and control system according to claim 7, characterized in that: The main platform is also used to: Obtaining the production preparation tasks corresponding to the target cross-platform common parts created by the primary control platform based on the design changes and the design change implementation nodes, and transmitting the production preparation tasks to the secondary control platform; Obtaining secondary control confirmation information sent by the secondary control platform based on the production preparation task; The secondary control confirmation information is transmitted to the main control platform so that the main control platform can control the trial installation verification, inventory quantity and switching time corresponding to the target cross-platform shared parts based on the secondary control confirmation information and the main control confirmation information corresponding to the production preparation task collected by the main control platform itself.

9. A cross-platform shared component design change implementation control device, characterized in that: include: A memory and a processor, wherein the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the cross-platform shared component design change implementation management method described in any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the cross-platform shared component design change implementation management method according to any one of claims 1 to 5.

Images