Demand change processing method and device and electronic equipment

Abstract

The invention relates to the technical field of program control, and discloses a demand change processing method and device and electronic equipment.The method comprises the steps that in response to a demand change request proposed by a user, an engineering change demand issuing process is entered; the demand change request comprises a changed demand; based on the changed demand, initiating a pre-review process through a fault diagnosis and prediction system; the pre-review process is used for generating a pre-review result based on a small piece trial assembly process; if the pre-review result indication is passed, creating a manufacturing demand change list based on the changed demand; carrying out production line trial assembly based on the manufacturing demand change list, and carrying out point inspection in the production line trial assembly process; and if the point inspection result indication is passed, automatically issuing the manufacturing demand change list. The method has the beneficial effect that the processing efficiency of demand change is improved.

Description

Technical Field

[0001] This application relates to the field of program control technology, and in particular to a method, apparatus and electronic device for handling demand changes. Background Technology

[0002] In the manufacturing sector, optimizing change management in production processes through digitalization can achieve end-to-end information integration and automated collaboration, thereby improving production efficiency. This change management approach is particularly suitable for complex manufacturing scenarios such as automotive OEMs.

[0003] Currently, change management typically employs an "offline forms + manual coordination" model. This model relies on the flow of documents such as trial installation applications and switchover coordination forms, and combines this with methods such as email and meetings to advance the work during the change process and implement the changes.

[0004] However, this approach suffers from inefficient change management, which can easily affect the development process of the vehicle's main unit. Summary of the Invention

[0005] This application provides a method, apparatus, and electronic device for handling requirement changes, which solves the technical problem of low efficiency in change management and achieves the technical effect of improving the efficiency of requirement change handling.

[0006] To achieve the above objectives, the main technical solutions adopted in this application include: In response to a user's request for a change of requirements, the process of publishing an engineering change request is initiated; the request for a change of requirements includes the changed requirements. Based on the changed requirements, a pre-review process is initiated through the fault diagnosis and prediction system; the pre-review process is used to generate pre-review results based on the small-piece trial assembly process. If the pre-review results indicate approval, a manufacturing requirement change order is created based on the changed requirements; production line trial assembly is carried out based on the manufacturing requirement change order, and spot checks are performed during the production line trial assembly process; If the inspection results indicate that the requirements are met, the manufacturing requirement change order will be automatically issued.

[0007] In this example, by integrating small-piece trial assembly and production line trial assembly inspection, and ensuring that both trial assembly results are passed, the method of releasing changed requirements is used to achieve automated closed-loop control of the requirement change process, thereby improving the control over the entire requirement change process and increasing the efficiency of requirement change management.

[0008] In one example, a pre-review process is initiated through a fault diagnosis and prediction system, including: The fault diagnosis and prediction system freezes the process for issuing engineering change requests. Automatically create pre-review forms; Initiate a small-scale trial assembly process and generate the small-scale trial assembly results; Based on the pre-review form and the small-piece trial assembly results, a pre-review result is generated.

[0009] In this example, by freezing the engineering change request release process and executing a small-scale trial assembly process, and generating pre-review results based on the small-scale trial assembly process, the risk of change requests is controlled in advance, the efficiency of change request processing is improved, and the effect of accurate and rapid decision-making on the changed requirements is achieved.

[0010] In one example, a small-piece trial assembly process is initiated, and the small-piece trial assembly result is generated, including: Automatically create and publish engineering change notices; the engineering change notice includes the software components and / or hardware components corresponding to the changed requirements; Freeze the release process of the engineering change notice and create a development breakpoint notice; the development breakpoint notice is used to prompt the development personnel to prepare the software components and / or hardware components corresponding to the changed requirements; Based on the software and / or hardware components corresponding to the changed requirements, small-scale trial assembly was carried out. Product and process verification were performed on the small-piece trial assembly process to obtain the small-piece trial assembly results.

[0011] In this example, by automatically creating manufacturing requirement change orders and R&D breakpoint notification orders, and by performing small-scale trial assembly and generating trial assembly results, the processing order of each step in the requirement change process is ensured, thereby improving the efficiency of change processing and ensuring the effectiveness of change processing.

[0012] In one example, production line trial assembly is performed based on the manufacturing requirement change order, including: Based on the aforementioned manufacturing requirement change order, a trial assembly application form is derived; Based on the aforementioned trial installation application form, initiate the trial installation application form release process and conduct trial installation on the production line; Based on the trial assembly results of the production line, a trial assembly report is derived and published.

[0013] In this example, by automating the generation of trial installation request forms, driving production line trial installation and generating trial installation reports, the trial installation process is executed efficiently, further improving the verification effect of requirement changes, enhancing the reliability of requirement changes, and improving the safety of equipment production based on the changes.

[0014] In one example, if the change in the requirement change request is a process change, the production line trial assembly is performed based on the manufacturing requirement change order, including: Based on the aforementioned manufacturing requirement change order, a process verification report is derived. Based on the process validation report, initiate the process validation report release process and conduct production line validation; Based on the production line validation results, a process validation report is issued.

[0015] In this example, for process changes, the automatic generation of process validation reports is used to drive the production line to perform validation during trial production. This enables the validation of the production process and products when process changes occur, improving the effectiveness and efficiency of process change management.

[0016] In one example, the method further includes: If the inspection results indicate that the project fails, the project will re-enter the engineering change request release process based on the user's request for change.

[0017] In this example, by automatically triggering the rollback process of the requirement change request when the inspection result fails, and optimizing and re-entering the release process, we can achieve a rapid response to change exceptions, improve the efficiency of change processing, and ensure the effectiveness of changes.

[0018] Secondly, embodiments of this application provide a demand change processing apparatus, including: The startup module is used to respond to user requests for change of requirements and initiate the engineering change request release process; the request for change of requirements includes the changed requirements. The pre-review module is used to initiate a pre-review process based on the changed requirements through the fault diagnosis and prediction system; the pre-review process is used to generate pre-review results based on the small-piece trial assembly process. The trial assembly module is used to create a manufacturing requirement change order based on the changed requirements if the pre-review results indicate that the changes are approved; to perform trial assembly on the production line based on the manufacturing requirement change order; and to conduct spot checks during the trial assembly process. The publishing module is used to automatically publish the manufacturing requirement change order if the inspection result indicates that it has passed.

[0019] In one example, the pre-review module is used for: The fault diagnosis and prediction system freezes the process for issuing engineering change requests. Automatically create pre-review forms; Initiate a small-scale trial assembly process and generate the small-scale trial assembly results; Based on the pre-review form and the small-piece trial assembly results, a pre-review result is generated.

[0020] In one example, the pre-review module is used for: Automatically create and publish engineering change notices; the engineering change notice includes the software components and / or hardware components corresponding to the changed requirements; Freeze the release process of the engineering change notice and create a development breakpoint notice; the development breakpoint notice is used to prompt the development personnel to prepare the software components and / or hardware components corresponding to the changed requirements; Based on the software and / or hardware components corresponding to the changed requirements, small-scale trial assembly was carried out. Product and process verification were performed on the small-piece trial assembly process to obtain the small-piece trial assembly results.

[0021] In one example, a trial module is used for: Based on the aforementioned manufacturing requirement change order, a trial assembly application form is derived; Based on the aforementioned trial installation application form, initiate the trial installation application form release process and conduct trial installation on the production line; Based on the trial assembly results of the production line, a trial assembly report is derived and published.

[0022] In one example, if the change in the requirement change request is a process change, a trial assembly is performed on the production line based on the manufacturing requirement change order. The trial assembly module is used for: Based on the aforementioned manufacturing requirement change order, a process verification report is derived. Based on the process validation report, initiate the process validation report release process and conduct production line validation; Based on the production line validation results, a process validation report is issued.

[0023] In one example, the publishing module is also used for: If the inspection results indicate that the project fails, the project will re-enter the engineering change request release process based on the user's request for change.

[0024] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the method described in any of the above embodiments.

[0025] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer instructions, which are used to cause a computer to perform the method described in any one of the above embodiments.

[0026] Fifthly, embodiments of this application provide a computer program product, including computer instructions, which are used to cause a computer to perform the method described in any of the above embodiments. Attached Figure Description

[0027] To more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings required for use in the description of the specific embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0028] Figure 1 It is a flowchart of the requirement change processing method provided by an embodiment of the present application; Figure 2 It is a flowchart of the regular change provided by an embodiment of the present application; Figure 3 It is a flowchart of the process change provided by an embodiment of the present application; Figure 4 It is a flowchart of the requirement change processing method provided by an embodiment of the present application; Figure 5 It is a flowchart of the production management provided by an embodiment of the present application; Figure 6 It is an interface diagram of the production management system provided by an embodiment of the present application; Figure 7 It is a module diagram of the requirement change processing device provided by an embodiment of the present application; [[ID=2)] Figure 8 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Specific Embodiments

[0029] [[ID=)0]]To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are some, rather than all, of the embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present application.

[0030] In the field of production and manufacturing, especially in the production and manufacturing process of automobile OEMs, requirement change, as a high-frequency and key business link, the quality of its full-process control directly affects production efficiency and product quality. However, the current industry generally faces multiple challenges: On the one hand, the volume of changes is large and relies on pure manual control, resulting in difficulty in ensuring the accuracy of changes. At the same time, the process is complex and the cycle is long. From the proposal of changes to the implementation and landing, it requires joint operations of more than a dozen departments such as R & D, engineering, procurement, quality, production, sales, and after-sales. The process tracking span is large and the cycle is long. The cross-department communication and coordination cost is high, information transmission is prone to distortion or delay, and the decision-making efficiency is low.

[0031] On the other hand, the implementation of changes still relies mainly on paper-based approvals and offline processes. Key forms such as trial installation applications and switchover coordination forms depend on email and paper documents, resulting in process gaps or insufficient connections, making it difficult to track status in real time and query historical records. Moreover, the disconnect between change data and processes creates a "two-layer" phenomenon, and relying solely on manual tracking can easily overlook potential risks.

[0032] The aforementioned problems have led to low management efficiency in the current production and manufacturing processes of automobile OEMs, and may even cause disconnection between upstream and downstream businesses, production line stoppages, and quality issues, becoming a key bottleneck restricting the digital transformation of the automotive manufacturing industry.

[0033] To address the aforementioned issues, this application proposes a method for handling requirement changes. This method establishes a fully online management approach for the entire requirement change process in the automotive industry. It not only enables fully online management of requirement changes but also facilitates data sharing across multiple systems, achieving closed-loop online control. During this process, ledgers and reports are automatically generated, process progress and operation history are automatically recorded, and historical operations are traceable while current operations are queryable. Furthermore, the execution of this process includes error prevention for processes and forms, ensuring process associativity, form mapping, and result notifications, thereby further improving human-computer interaction capabilities and better assisting users in handling requirement changes.

[0034] Furthermore, the requirement change processing method of this application can also support the execution of different change processes, ensuring the online realization of the entire production process, improving the efficiency of requirement change processing, and improving the production efficiency of automobiles.

[0035] According to an embodiment of this application, a method for handling requirement changes is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0036] According to an embodiment of this application, the requirement change processing method can be executed on an electronic device. This electronic device can be a computer, server, terminal device, or other device with a certain computing power. The requirement change processing system provided in this application can be deployed on the electronic device. Based on this change processing system, the electronic device can interact with the user, thereby further improving the efficiency of requirement change processing.

[0037] Figure 1 A flowchart of the requirement change processing method provided in the embodiments of this application is shown below. Figure 1 As shown, with electronic devices as the executing entity, this process includes the following steps: S101. In response to a user's request for a change of requirements, the process of issuing an engineering change request is initiated. The request for a change of requirements includes the revised requirements.

[0038] For example, after receiving a user's request for a change of requirements, the electronic device can respond to the request by initiating an engineering change requirement release process.

[0039] In one implementation, users can submit a request to change their requirements by inputting the changed requirements in the interactive interface.

[0040] In one implementation, the electronic device can obtain a user-triggered requirement change request and parse it to obtain the changed requirements contained therein. Based on these changed requirements, the electronic device can complete the initial registration and process triggering of the requirement change and enter the engineering change requirement release process.

[0041] In one implementation, the requirement for change can be a change to elements such as product function, performance, and process.

[0042] In one implementation, the change request may include core information such as the reason for the change and the scope of the change, in addition to the changed requirements.

[0043] In one implementation, the changed requirements can characterize the functions, performance, and processes that the user expects to use.

[0044] In one implementation, the change request may also include information such as the changed expected parameters and anticipated effects.

[0045] In one implementation, the user can input and submit the requirement change request through the interactive interface of the production management system running on the electronic device.

[0046] In one implementation, the requirement change handling method of this application can be embedded in the production management system.

[0047] S102. Based on the changed requirements, initiate a pre-review process through the fault diagnosis and prediction system. The pre-review process is used to generate pre-review results based on the small-piece trial assembly process.

[0048] For example, after receiving the change request, the electronic device can obtain the revised requirements from it. The electronic device can then generate and initiate a pre-review process for the revised requirements through a pre-defined fault diagnosis and prediction system.

[0049] In one implementation, the pre-review process can specifically involve verifying the performance of a product with the changed requirements during production and use through small-scale trial assembly. Electronic devices can then generate pre-review results based on these verification results.

[0050] In one implementation, the pre-review result may include the equipment stability, process parameters, and product quality corresponding to the changed performance. Furthermore, the pre-review result may also include the potential impact of the changed performance on equipment stability, process parameters, and product quality, obtained by comparing the equipment stability, process parameters, and product quality before and after the change. Moreover, the pre-review result may also include a risk level and improvement suggestions generated based on the above information.

[0051] In one implementation, the fault diagnosis and prediction system is a system running inside the electronic device. This fault diagnosis and prediction system can be two systems that are independent of and mutually call upon the production management system.

[0052] In one implementation, the fault diagnosis and prediction system can construct a virtual trial assembly environment based on current production data using digital twin technology, or call historical trial assembly data to train a prediction model to simulate the product, thereby achieving fault diagnosis and prediction based on the simulated product.

[0053] In another implementation, the fault diagnosis and prediction system can also perform fault diagnosis and prediction based on a physical sample of the product.

[0054] In one implementation, the small-piece trial assembly process refers to the process of assembling a small batch of products with changed requirements in a laboratory or simulated production line environment. The assembled product can be the entire product. Alternatively, the assembled product can be a component involved in the changed requirements.

[0055] S103. If the pre-review results indicate approval, a manufacturing requirement change order (MCO) is created based on the revised requirements. Trial assembly is then conducted on the production line based on the MCO, and inspections are performed during the trial assembly process.

[0056] For example, if the pre-review result indicates that the device passes, the electronic device can perform subsequent testing and / or production according to a preset process.

[0057] When the pre-review results indicate approval, a Manufacturing Requirement Change Order (MCO) can be created based on the revised requirements for electronic equipment. This MCO instructs the production line to produce according to the revised requirements.

[0058] The electronic equipment can instruct the production line to perform trial assembly based on the manufacturing requirement change order. The electronic equipment can also inspect the trial-assembled products to determine the effectiveness of the trial assembly.

[0059] In one implementation, a Manufacturing Requirements Change Order (MCO) is a standardized document that records the changes, implementation plan, and responsible department. This MCO serves as the basis for production line execution. Furthermore, the production line can initiate production based on this MCO.

[0060] In one implementation approach, production line trial assembly refers to the stage of verifying changed requirements in a small batch within a real production environment. This process involves equipment debugging, process parameter optimization, and personnel training.

[0061] In one implementation, spot inspection refers to testing key quality indicators of the trial-assembled product during the trial assembly process.

[0062] Optionally, this inspection can be a step-by-step check of key points on the trial-assembled product. Optionally, these key points may include indicators such as equipment operating status, product dimensional accuracy, and process stability.

[0063] In one implementation, the manufacturing requirement change order can be automatically generated by the production management system based on the changed requirements. S104. If the inspection result indicates that the inspection is passed, a manufacturing requirement change order will be automatically issued.

[0064] For example, if the inspection result indicates that the change has been completed, it means that the change requirement has been finalized and mass production can officially begin. At this point, the electronic device can automatically issue a manufacturing requirement change order, completing the closed-loop management of the change process.

[0065] In one implementation, issuing the manufacturing requirement change order means that the manufacturing requirement change order will be formally incorporated into the production execution system and enter the production process.

[0066] In one implementation, after the manufacturing requirement change order is issued, the production management system can update the associated data such as process documents, equipment parameters, and quality standards already stored in the production management system based on the information such as processes, parameters, and quality indicators included in the manufacturing requirement change order.

[0067] In one implementation, the process of issuing the manufacturing requirement change order can be implemented through the production management system.

[0068] In this embodiment, by integrating small-piece trial assembly and production line trial assembly inspection, and when both trial assembly results pass, the method of releasing changed requirements is used to achieve automated closed-loop control of the requirement change process, thereby improving the control of the entire requirement change process and improving the efficiency of requirement change management.

[0069] In one example, step S102 above, which involves initiating a pre-review process through a fault diagnosis and prediction system, specifically includes: S1021, The process for releasing engineering change requests in the fault diagnosis and prediction system is frozen.

[0070] For example, when an electronic device invokes a fault diagnosis and prediction system, it can freeze the engineering change request release process so that the electronic device can continue to execute subsequent steps after determining that the pre-review process has been completed.

[0071] In one implementation, freezing the engineering change request release process can prevent changed requirements from being applied to production without passing pre-review, thus avoiding waste of production resources or quality incidents.

[0072] S1022. Automatically create pre-review forms.

[0073] For example, electronic devices can automatically create a pre-review form after entering the pre-review process.

[0074] In one implementation, the pre-review form can be used to transform the changed requirements into a structured review document.

[0075] In one implementation, the pre-review form can be a standardized form that includes review items, responsible persons, and completion deadlines.

[0076] In one implementation, the pre-review form can also be used to record the preliminary assessment results of the change. Its content may cover the necessity of the change, feasibility analysis, and potential risks.

[0077] In one implementation, electronic devices can parse the changed requirements through a rules engine and generate a pre-review form based on the parsing results and a preset review template.

[0078] In one implementation, the rule engine can parse the changed requirements using natural language processing technology. Alternatively, the rule engine can parse the changed requirements using keyword extraction.

[0079] S1023, Initiate the small piece trial assembly process and generate the small piece trial assembly results.

[0080] For example, an electronic device can initiate a small-piece trial assembly process. During the small-piece trial assembly process, the electronic device can detect the parameters of the installation process and the parameters of the installed product, and obtain the small-piece trial assembly result.

[0081] In one implementation, the small-piece trial assembly process refers to a partial verification stage for design changes, typically involving production testing of a single device, a single workstation, or a small number of batches.

[0082] In one implementation, the small-scale trial assembly result refers to a report that records indicators such as equipment operating status, process parameter stability, and product qualification rate during the trial assembly process, including success / failure conclusions and improvement suggestions.

[0083] In one implementation, the small-scale trial fitting process can utilize digital twin technology to construct a virtual trial fitting environment, thereby reducing the consumption of physical resources.

[0084] In another implementation method, the small-piece trial assembly process can also be carried out in an isolated area of ​​a dedicated test line or main production line. In one implementation, the trial assembly results can be generated using various data acquisition methods, such as manual recording, automatic sensor acquisition, or AI visual inspection.

[0085] S1024. Generate pre-review results based on the pre-review form and the small-piece trial assembly results.

[0086] For example, an electronic device can extract the content that needs to be filled in the pre-review form from the results of a small sample assembly, thereby generating a pre-review result.

[0087] In one implementation, the electronic device can integrate technical feasibility analysis and actual verification data to determine whether the change request meets the conditions for production implementation, and generate an output containing a risk level, improvement measures, and approval recommendations. The electronic device can then write this result into the pre-approval result.

[0088] In one implementation, the pre-review result refers to the assessment opinion generated regarding whether the changed requirements can proceed to the next stage. This pre-review result can include multiple categories such as "passed," "conditionally passed," and "not passed."

[0089] In one implementation, the electronic device can obtain the pre-review result through statistical analysis of the small-piece trial assembly results.

[0090] In another implementation, the electronic device can extract the content corresponding to the item in the pre-review form from the small sample trial assembly results and fill the pre-review form with the content to generate the pre-review result.

[0091] In another implementation, the electronic device can output the pre-review results by inputting the installation process parameters, process parameters, product parameters, etc., included in the small-piece trial assembly results into the large model.

[0092] In this example, by freezing the engineering change request release process and executing a small-scale trial assembly process, and generating pre-review results based on the small-scale trial assembly process, the risk of change requests is controlled in advance, the efficiency of change request processing is improved, and the effect of accurate and rapid decision-making on the changed requirements is achieved.

[0093] In one example, in step S1023 above, the electronic device can initiate a small-piece trial assembly process, and generate a small-piece trial assembly result based on this process. This process may include: S10231. Automatically create and publish engineering change orders. Engineering change orders include the software components and / or hardware components corresponding to the changed requirements.

[0094] For example, after determining to initiate a small-piece trial assembly process, the electronic device can first automatically create and publish an engineering change notice.

[0095] In one implementation, the engineering change notification form is a formal document used by the user to record changes to the product's software and hardware. The engineering change notification form may include information covering the reason for the change, the scope of impact, implementation steps, and the responsible party.

[0096] In one implementation, software components refer to program modules or firmware that implement product functions. Hardware components refer to physical parts or devices that constitute the product.

[0097] In one implementation, the electronic device can also send the engineering change notice to the corresponding responsible person after generating it, so that the responsible person can perform the corresponding change processing according to the engineering change notice.

[0098] In one implementation, the electronic device can send the engineering change notification through the production management system. Alternatively, the electronic device can send the engineering change notification through pre-set communication software. Or, the electronic device can send the engineering change notification through pre-set email, SMS, or other methods.

[0099] S10232. Freeze the release process of Engineering Change Notices and create a Development Breakpoint Notice. The Development Breakpoint Notice is used to prompt developers to prepare the software and / or hardware components corresponding to the changed requirements.

[0100] For example, the electronic device can freeze the release process of the Engineering Change Notice (ECD) after it has been sent. Subsequently, the electronic device can create a Development Breakpoint Notice. The electronic device can then send this Development Breakpoint Notice to the corresponding R&D personnel, enabling them to complete the corresponding R&D tasks based on the changed requirements.

[0101] In one implementation, if the changed requirement is a software requirement, developers can write, test, and package the software component based on the changed requirement to generate a usable software version. This usable software version is denoted as the software component corresponding to the changed requirement.

[0102] In one implementation, if the changed requirement is a hardware requirement, the R&D personnel can produce, manufacture, or procure the hardware component based on the changed requirement to obtain a usable hardware component.

[0103] In one implementation, freezing the process of issuing engineering change orders can suspend the formal effectiveness of the change orders, allowing the R&D department time to develop or adjust components.

[0104] Optionally, the freezing process specifically involves locking the status of a change order through the workflow engine, preventing it from proceeding to the next stage of operation.

[0105] Optionally, the freezing process can be configured to automatically resume the issuance of engineering change notices when the unfreezing conditions are met. Alternatively, the freezing process can be configured to allow users with unfreezing permissions to unfreeze the system and then resume the issuance of engineering change notices.

[0106] In one implementation, the development breakpoint notification form refers to a notification file that prompts developers to start component development. It may include a description of the change requirements, technical specifications, and delivery timelines.

[0107] S10233. Based on the software components and / or hardware components corresponding to the changed requirements, conduct small-scale trial assembly.

[0108] For example, electronic devices can initiate a small-piece trial assembly process based on the software and / or hardware components corresponding to the changed requirements.

[0109] In one implementation, the small piece can be tested in a test environment or an isolated area of ​​the main production line.

[0110] In one implementation, software component trial installation refers to loading a new version of the program or firmware onto the test device. Hardware component trial installation refers to installing a new component onto a simulation fixture or actual equipment.

[0111] In one implementation, the trial installation environment can use digital twin technology to construct a virtual product, reducing the consumption of physical resources.

[0112] In another implementation method, the actual deployment of products can also be carried out at a dedicated test line or a spare workstation on the main production line.

[0113] In one implementation, the trial installation process can rely on automated scripts to complete component installation and configuration, or be manually operated by technicians who record parameters.

[0114] S10234. Verify the product and process during the small-piece trial assembly process to obtain the small-piece trial assembly results.

[0115] For example, electronic devices can use a fault diagnosis and prediction system to perform product and process verification on the small-piece trial assembly process and generate small-piece trial assembly results containing qualification conclusions.

[0116] In one implementation, the trial assembly results of the small piece may include data such as the function, performance, and process stability of the trial assembly product.

[0117] In one implementation, product verification may specifically include functional testing, performance index detection, and reliability assessment of the trial-assembled samples. Process verification may specifically include checking equipment operating procedures, process parameter control, and personnel proficiency during the trial assembly process.

[0118] In one implementation, the small-piece trial assembly result includes functional test parameters, performance indicators, reliability assessment results, operational data, process parameters, and operator proficiency assessment results collected during the verification process. Furthermore, the small-piece trial assembly result may also include a pass / fail assessment conclusion obtained based on the above data analysis, and improvement suggestions generated based on the assessment results.

[0119] In one implementation, the results of the small-piece trial assembly can be a form containing multiple conclusions generated based on a preset model.

[0120] In this example, by automatically creating manufacturing requirement change orders and R&D breakpoint notification orders, and by performing small-scale trial assembly and generating trial assembly results, the processing order of each step in the requirement change process is ensured, thereby improving the efficiency of change processing and ensuring the effectiveness of change processing.

[0121] In one example, step S103 above, which involves trial assembly of the production line based on a manufacturing requirements change order, includes the following process: S1031. Based on the manufacturing requirement change order, a trial assembly application form is derived.

[0122] For example, an electronic device generates a trial assembly application form based on a manufacturing requirement change order, according to a preset procedure.

[0123] In one implementation, the derivation of the trial installation application form means transforming the change request into an executable trial installation task instruction.

[0124] In one implementation, the trial installation application form refers to the application document for initiating a trial installation task, which clearly defines the purpose of the trial installation, the trial installation target, and the acceptance criteria.

[0125] In one implementation, a manufacturing requirement change order refers to a formal document that records changes in the product manufacturing process, covering specific requirements such as process adjustments, equipment replacements, or material substitutions.

[0126] In one implementation, the electronic device can automatically generate the trial installation application form by extracting key information from the change order and automatically filling it into a preset template.

[0127] S1032. Based on the trial installation application form, initiate the trial installation application form release process and conduct trial installation on the production line.

[0128] For example, an electronic device can initiate a trial installation application process based on a trial installation application form. After completing the trial installation application process, the electronic device can start the production line trial installation task and perform the production line trial installation.

[0129] In one implementation, the trial installation application form release process refers to the entire process management from application form submission to the initiation of the trial installation task. This trial installation application form release process may include approval, resource allocation, and task assignment.

[0130] In one implementation, production line trial installation refers to the process of batch verification of change requirements in a real production environment, involving equipment debugging, process parameter optimization, and personnel training.

[0131] S1033. Based on the trial assembly results of the production line, derive and publish the trial assembly report.

[0132] For example, electronic devices can generate production line trial assembly results based on the production line trial assembly process and the products obtained from the trial assembly. Electronic devices can then derive and publish trial assembly reports based on these results.

[0133] In one implementation, the production line trial assembly result refers to a data set recording the equipment status, product quality, and process stability during the trial assembly process. And / or, the production line trial assembly result may also include data such as the quality, yield, and parameters of the product obtained during the trial assembly. And / or, the production line trial assembly result may also include outcome parameters obtained based on the above data analysis. For example, these outcome parameters may include the impact coefficient of changed requirements on product quality, etc.

[0134] In one implementation, the trial installation report refers to a conclusive document generated after a systematic analysis of the trial installation results. It typically includes information on the achievement of trial installation objectives, records of abnormal events, and subsequent action plans. The trial installation report may include information such as qualification assessment, problem analysis, and optimization measures.

[0135] In one implementation, the trial installation report may have a fixed format template.

[0136] In one implementation, the trial fitting report can be generated by automatically extracting trial fitting data and filling a preset template through the system. Alternatively, the trial fitting report can be generated by intelligently analyzing the data using AI algorithms.

[0137] In one implementation, the release of the trial installation report may include email notifications, system message pushes, or integrated storage with the enterprise knowledge base.

[0138] In this example, by automating the generation of trial installation request forms, driving production line trial installation and generating trial installation reports, the trial installation process is executed efficiently, further improving the verification effect of requirement changes, enhancing the reliability of requirement changes, and improving the safety of equipment production based on the changes.

[0139] In one example, if the change in the requirement change request is a process change, then step S103 above, the process of conducting production line trial assembly based on the manufacturing requirement change order, includes: S1034. Based on the manufacturing requirement change order, derive a process verification report.

[0140] For example, if the change in the requirement change request is a process change, the electronic device can generate a blank form of the process verification report based on the manufacturing requirement change order and according to a preset template format.

[0141] In one implementation, the blank form of the process verification report is used to fill in the verification data during the verification process in step S1035.

[0142] In one implementation, the process validation report includes a standardized document outlining the validation objectives, methods, and expected results.

[0143] S1035. Based on the process validation report, initiate the process validation report release process and conduct production line validation.

[0144] For example, an electronic device initiates a process validation report release process based on a process validation report. In this process, the electronic device can acquire parameters during the trial production process on the production line and use these parameters to complete the process validation report. The electronic device can then complete production line validation based on the completed process validation report.

[0145] In one implementation, the process validation report release process refers to the entire process management from report submission to production line validation initiation, including cross-departmental review, resource coordination, and task assignment.

[0146] In one implementation, production line verification refers to the process of monitoring the equipment involved in the batch trial production of the changed process in a real production environment to obtain the equipment debugging parameters, and then sampling the produced products to obtain the product parameters.

[0147] In one implementation, electronic devices can push the process verification report to the approval node. After joint confirmation by the technical, production, and quality departments, production line resources are scheduled to execute the actual process verification.

[0148] S1036. Based on the production line verification results, issue a process verification report.

[0149] For example, electronic devices can fill out a process verification report based on production line verification results, and then publish a process verification report containing specific parameters.

[0150] In one implementation, the production line verification result refers to the data set that records the process stability, product quality, and production efficiency during the verification process.

[0151] Optionally, the dataset may also include equipment operation logs, product testing reports, and process parameter records.

[0152] In one implementation, the process validation report refers to a conclusive document formed after a systematic analysis of the validation results. It typically includes the achievement of validation objectives, records of abnormal event handling, and recommendations for subsequent process solidification.

[0153] In one implementation, the process verification report in this step is a form completed after filling out the empty form in step S1024.

[0154] In one implementation, the process verification report can be generated either by automatically extracting verification data from the system and filling a preset template, or by using AI algorithms to intelligently analyze the data.

[0155] In one implementation, the process validation report may be published via email notification, system message push, or integrated storage with an enterprise document management system.

[0156] In this example, for process changes, the automatic generation of process validation reports is used to drive the production line to perform validation during trial production. This enables the validation of the production process and products when process changes occur, improving the effectiveness and efficiency of process change management.

[0157] In one example, if the inspection result indicates a failure, the requirement change processing procedure may also include the following steps: S104. If the inspection result indicates that the test is not passed, the process will be restarted based on the user's request for change of requirements.

[0158] For example, when an electronic device determines that an inspection result is unsuccessful, a reprocessing mechanism based on a user-required change request can be automatically triggered. This reprocessing mechanism can guide the process to the requirement change release stage, where the specific implementation of the requirement change can be adjusted and optimized based on the inspection result, so that the product after the requirement change can meet the testing requirements.

[0159] In one implementation, the inspection result refers to the conformity judgment data generated after periodic inspections of equipment, processes, or products. This inspection result typically includes comparisons of test indicators, actual values, and standard values.

[0160] In one implementation, a change request refers to a user's modification request for the existing production or product status, which may involve functional expansion, performance improvement, or compliance adjustments.

[0161] In one implementation, the engineering change request release process refers to the full-process management from the submission of the change request to the final implementation, covering the approval, resource coordination, verification and release stages.

[0162] In one implementation, the process of re-executing the engineering change request release process can be a process of adjusting and optimizing the change request through manual intervention. Alternatively, the process of re-executing the engineering change request release process can be a process of adjusting and optimizing the implementation process of the changed requirement.

[0163] For example, the parameters of the hardware components corresponding to the changed requirements can be adjusted to obtain hardware components that meet the changed requirements and can optimize the abnormalities that occur during the inspection process.

[0164] For example, the software components corresponding to the changed requirements can be iterated to obtain software components that meet the changed requirements and can optimize the anomalies that occur during the inspection process.

[0165] In one implementation, this process can be achieved by updating the engineering change order. For example, parameters in the engineering change order can be changed, or new parameters can be added to the engineering change order.

[0166] In one implementation, if the number of times the engineering change request release process is re-entered exceeds a preset number, the electronic device can end the current request update and indicate that the request update has failed.

[0167] Optionally, the electronic device can also generate a report of failed demand updates.

[0168] In this example, by automatically triggering the rollback process of the requirement change request when the inspection result fails, and optimizing and re-entering the release process, we can achieve a rapid response to change exceptions, improve the efficiency of change processing, and ensure the effectiveness of changes.

[0169] Figure 2 A flowchart illustrating a routine modification provided for an embodiment of this application. Using an electronic device as the executing entity, in... Figure 1 Based on the illustrated embodiments, as Figure 2 As shown, the process may include: S201. In response to a user's request for an update, the electronic device creates an engineering change request and initiates an engineering change request release process.

[0170] S202. After electronic equipment enters the engineering change request release process, the engineering change notification form is frozen, and a pre-review form is automatically created. The user maintains the pre-review form and initiates the pre-review form release process.

[0171] S203. The electronic device automatically creates an Engineering Change Notice and initiates the process of freezing the Engineering Change Notice. Subsequently, the electronic device organizes a change committee, and after the change committee is formed, automatically issues the Engineering Change Notice.

[0172] S204. Electronic devices can perform small-scale trial assembly. Before small-scale trial assembly, electronic devices can automatically create R&D breakpoint notification forms and initiate the R&D breakpoint notification form release process.

[0173] S205. After a small-scale trial assembly, the electronic equipment can automatically create a manufacturing requirement change order. After maintaining the manufacturing requirement change order, the electronic equipment can initiate the manufacturing requirement change order release process.

[0174] S206. If the electronic device enters the trial assembly stage, proceed to step S207. If the electronic device does not enter the trial assembly stage, proceed to step S208.

[0175] S207. Electronic devices can generate trial installation application forms and initiate the trial installation application form release process. Electronic devices can also generate trial installation reports and initiate the trial installation report release process.

[0176] S208. After the electronic equipment completes the inspection, a manufacturing change order is automatically issued.

[0177] S209. Derive work orders from electronic devices and initiate the work order release process.

[0178] Figure 3 A flowchart illustrating the process change provided in this application's embodiments. Using an electronic device as the executing entity, in... Figure 1 Based on the illustrated embodiments, as Figure 3 As shown, the process may include: S301. Create a process change request for electronic equipment and initiate the process change request release process.

[0179] S302. If the electronic device enters the trial assembly stage, proceed to step S303. If the electronic device does not enter the trial assembly stage, proceed to step S304.

[0180] S303, derive process verification report for electronic equipment and initiate process verification report release process.

[0181] S304. Derive production orders for electronic devices and issue production orders.

[0182] In this embodiment, through the processes of routine changes and process changes, a high degree of integration of the change process into the production management system is achieved, enabling paperless operation and breaking down information silos between different stages. This requirement change handling method, based on the production management system, realizes integrated automated execution of requirement change tracking, follow-up, management, and control, improving the efficiency, accuracy, and effectiveness of change processing.

[0183] Figure 4 The flowchart of the requirement change processing method provided in the embodiments of this application uses an electronic device as the execution subject. Figures 1 to 3 Based on the illustrated embodiments, as Figure 4 As shown, based on the business implementation scenario, the change handling process is described, including: Electronic equipment completes the process of changing requirements in production management through three steps: solution formulation, real-time preparation, and implementation and switchover.

[0184] The process of developing a solution can include submitting a change request and obtaining an efficient customer response. Based on this request and response, the electronic device can then obtain the finalized change plan and undergo cross-departmental review and approval by the change committee. Ultimately, the electronic device can then issue an engineering change order.

[0185] During the real-time preparation process, the electronic equipment can execute the changes in two separate ways after receiving the engineering change order.

[0186] Firstly, the electronic equipment can perform small-scale trial assembly. Before executing the trial assembly, it can obtain breakpoint VIN feedback. After the trial assembly, it can send data and supplier change notifications. After receiving confirmation of the supplier change receipt, it can perform trial assembly using the modified components supplied by the supplier. It can conduct a material inventory check before trial assembly. Alternatively, it can execute a trial assembly request and obtain the trial assembly results beforehand. If the trial assembly result indicates success, it can conduct a material inventory check. If the trial assembly result indicates failure, it can handle any issues that arise during the trial assembly. If the issue is a design problem, it can reissue the engineering change order. If the issue is a trial assembly problem, it can re-perform the trial assembly. After completing the material inventory check, it can issue a switchover order.

[0187] Secondly, electronic equipment can issue a switchover order after engineering approval, production part approval procedure approval, parts inspection standard update, supplier notification for the first batch of delivery, parts arrival confirmation, regulatory certification document update, and assembly and commissioning manual update.

[0188] During the switchover process, the electronic equipment can acquire published work orders and process corresponding inventory. Based on these work orders, it can also perform operations such as updating in-plant fabric identification, updating incoming material inspection documents, updating process documents, updating vehicle inspection documents, updating in-process inspection documents, supplier breakpoint identification, publishing software material lists, and updating bills of materials. Subsequently, it can process the first batch of incoming parts receiving and online identification. Furthermore, it can perform one-vehicle-one-BOM updates and breakpoint VIN feedback.

[0189] In this embodiment, the specific processing of requirement changes in production management is realized through three steps: solution formulation, real-time preparation, and implementation and switchover, thereby improving the efficiency of change management.

[0190] Figure 5 The production management flowchart provided in this application embodiment uses electronic devices as the execution subject. Figures 1 to 4 Based on the illustrated embodiments, as Figure 5 The diagram illustrates the workflow allocation across the three steps of solution development, real-time preparation, and implementation / switchover in a production management system. This includes: The solution development phase is led by R&D engineers. This includes: R&D personnel can execute the solution development and release tracking process. Product development teams can execute steps such as solution review and approval, process modification judgment, and work execution judgment. Procurement personnel can execute supplier inventory statistics and collect change quotes. Planning and logistics personnel can execute factory inventory statistics and provide expected switchover dates. Cost management personnel can perform operations to evaluate expenses and cost changes. After-sales personnel can compile spare parts inventory statistics.

[0191] The preparation phase is led by the planning and logistics engineer. This includes: The logistics planning team can handle steps such as sample procurement, factory inventory management, trial assembly organization, and issuing changeover coordination orders. The R&D team can handle steps such as 2D / 3D design release, mold opening / repair tracking, ESO approval, and design document updates. The quality management team can handle trial assembly applications, PPAP approval, and update checks. The vehicle quality management team can handle sample inspection and trial assembly result assessment. The purchasing department can handle design change notifications. The product certification department can complete certification. The engineering and manufacturing department can handle tooling and equipment modifications.

[0192] The switchover was led by manufacturing engineers. This included: The manufacturing department performs operations such as issuing MWO (Manufacturing Notice), pre-changeover inspection, on-site preparation confirmation, updating the BOM (Bill of Materials) for each vehicle, and recording breakpoints. The planning and materials team performs material tracking and disposal. The process department performs process modification and updates process documents. The process quality management department updates process inspection documents. The vehicle quality management department updates inspection documents and updates inspection equipment.

[0193] In this embodiment, the responsibilities at each extreme of the business are implemented, the responsibilities of technical personnel at each stage of the entire production management process are divided, the collaboration efficiency of technical personnel is improved, and the efficiency of production management and change handling is improved.

[0194] Figure 6 The interface diagram of the production management system provided in this application embodiment uses electronic devices as the execution entity. Figures 1 to 5 Based on the illustrated embodiments, as Figure 6 As shown, the deployment of the interface for this production management system may include: The interface of this production management system can include four parts. The area within the dashed box on the left side of the interface represents the first menu area. The area within the dotted box represents the second menu area. The area within the dotted box with one dot interval represents the change information display area. The area within the dotted box with two dots represents the functional module area. Users can click on the code or name in the change information display area to view the change item corresponding to that code or name.

[0195] Accordingly, please refer to Figure 7 This application provides a requirement change processing apparatus 700, which includes: Module 701 is used to respond to user-submitted change requests and initiate the engineering change request release process. The change request includes the revised requirements.

[0196] The pre-review module 702 is used to initiate a pre-review process based on the changed requirements through the fault diagnosis and prediction system. The pre-review process generates pre-review results based on the small-piece trial assembly process.

[0197] The trial assembly module 703 is used to create a manufacturing requirement change order based on the changed requirements if the pre-review results indicate approval. Trial assembly is then performed on the production line based on the manufacturing requirement change order, and inspections are conducted during the trial assembly process.

[0198] The release module 704 is used to automatically release a manufacturing requirement change order if the inspection result indicates that it has passed.

[0199] In one example, the pre-review module 702 is used for: The fault diagnosis and prediction system freezes the process for issuing engineering change requests.

[0200] Automatically create pre-review forms.

[0201] Initiate a small-scale trial assembly process and generate the small-scale trial assembly results.

[0202] Based on the pre-review form and the results of the small-scale trial assembly, the pre-review results are generated.

[0203] In one example, the pre-review module 702 is used for: Automatically create and publish Engineering Change Notices. Engineering Change Notices include the software and / or hardware components corresponding to the changed requirements.

[0204] Freeze the process of issuing Engineering Change Notices and create Development Breakpoint Notices. Development Breakpoint Notices are used to prompt developers to prepare the corresponding software and / or hardware components for the changed requirements.

[0205] Based on the software and / or hardware components corresponding to the changed requirements, conduct small-scale trial assembly.

[0206] Product and process verification were performed on the small-piece trial assembly process to obtain the small-piece trial assembly results.

[0207] In one example, the trial module 703 is used for: A trial assembly application form is derived from the manufacturing requirement change order.

[0208] Based on the trial installation application form, initiate the trial installation application form release process and conduct trial installation on the production line.

[0209] Based on the trial assembly results of the production line, a trial assembly report is derived and published.

[0210] In one example, if the change in the requirement change request is a process change, a trial assembly is performed on the production line based on the manufacturing requirement change order. The trial assembly module 703 is used for: A process verification report is derived based on the manufacturing requirement change order.

[0211] Based on the process validation report, initiate the process validation report release process and conduct production line validation.

[0212] Based on the production line validation results, a process validation report is issued.

[0213] In one example, the 704 release module is also used for: If the inspection results indicate that the project fails, the process will be restarted based on the user's request for a change of requirements.

[0214] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0215] In this embodiment, the demand change processing device is presented in the form of a functional unit. Here, a functional unit refers to an application-specific integrated circuit (ASIC), a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0216] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 8 As shown, the electronic device includes one or more processors 801, a memory 802, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the electronic device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple electronic devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 8 Take the 801 processor as an example.

[0217] Processor 801 may be a central processing unit, a network processor, or a combination thereof. Processor 801 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0218] The memory 802 stores instructions executable by at least one processor 801 to cause the at least one processor 801 to perform the method shown in the above embodiments.

[0219] The memory 802 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the electronic device. Furthermore, the memory 802 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 802 may optionally include memory remotely located relative to the processor 801, and these remote memories can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0220] The memory 802 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 802 may also include a combination of the above types of memory.

[0221] The electronic device also includes a communication interface 803 for communicating with other devices or communication networks.

[0222] This application also provides a computer-readable storage medium. The methods described in this application can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code downloaded over a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and subsequently stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the methods shown in the above embodiments are implemented.

[0223] This application provides a computer program product including computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the method of any embodiment of this application.

[0224] Although embodiments of this application have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of this application, and all such modifications and variations fall within the scope defined by the appended claims.

[0225] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0226] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0227] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0228] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0229] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0230] It is understood that in the specific implementation of this application, data such as user information, location information, and navigation data are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0231] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0232] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0233] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0234] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0235] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0236] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0237] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0238] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0239] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

[0240] Although embodiments of this application have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of this application, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A demand change processing method characterized by comprising: The method comprises: entering an engineering change requirement publishing process in response to a requirement change request raised by a user; the requirement change request comprising a changed requirement; initiating a pre-evaluation process by a fault diagnosis and prediction system based on the changed requirement; the pre-evaluation process being used to generate a pre-evaluation result based on a small piece trial fitting process; if the pre-evaluation result indicates passing, creating a manufacturing requirement change order based on the changed requirement; conducting line trial fitting based on the manufacturing requirement change order, and conducting spot inspection in the line trial fitting process; if the spot inspection result indicates passing, automatically publishing the manufacturing requirement change order.

2. The method of claim 1, wherein, The method of initiating a pre-evaluation process by a fault diagnosis and prediction system comprises: freezing an engineering change requirement publishing process by a fault diagnosis and prediction system; automatically creating a pre-evaluation order; initiating a small piece trial fitting process, and generating a small piece trial fitting result; generating a pre-evaluation result according to the pre-evaluation order and the small piece trial fitting result.

3. The method of claim 2, wherein, The method of initiating a small piece trial fitting process, and generating a small piece trial fitting result comprises: automatically creating and publishing an engineering change notification order; the engineering change notification order comprising a software component and / or a hardware component corresponding to the changed requirement; freezing a publishing process of the engineering change notification order, and creating a research and development breakpoint notification order; the research and development breakpoint notification order being used to prompt a research and development personnel to prepare the software component and / or the hardware component corresponding to the changed requirement; conducting small piece trial fitting based on the software component and / or the hardware component corresponding to the changed requirement; conducting product and process verification on the small piece trial fitting process, and obtaining a small piece trial fitting result.

4. The method according to any one of claims 1 to 3, characterized in that, The method of conducting line trial fitting based on the manufacturing requirement change order comprises: deriving a trial fitting application order based on the manufacturing requirement change order; initiating a trial fitting application order publishing process based on the trial fitting application order, and conducting line trial fitting; deriving and publishing a trial fitting report based on a line trial fitting result.

5. The method according to any one of claims 1-3, characterized in that, If the change content in the requirement change request is process change, the method of conducting line trial fitting based on the manufacturing requirement change order comprises: deriving a process verification report based on the manufacturing requirement change order; initiating a process verification report publishing process based on the process verification report, and conducting line verification; publishing a process verification report based on a line verification result.

6. The method according to any one of claims 1-3, characterized in that, The method further comprises: if the spot inspection result indicates not passing, re-entering an engineering change requirement publishing process based on the requirement change request raised by the user.

7. A demand change processing apparatus characterized by comprising: The apparatus comprises: a starting module configured to enter an engineering change requirement publishing process in response to a requirement change request raised by a user; the requirement change request comprising a changed requirement; a pre-evaluation module configured to initiate a pre-evaluation process by a fault diagnosis and prediction system based on the changed requirement; the pre-evaluation process being used to generate a pre-evaluation result based on a small piece trial fitting process; a trial fitting module configured to, if the pre-evaluation result indicates passing, create a manufacturing requirement change order based on the changed requirement; conduct line trial fitting based on the manufacturing requirement change order, and conduct spot inspection in the line trial fitting process; a publishing module configured to, if the spot inspection result indicates passing, automatically publish the manufacturing requirement change order.

8. An electronic device, comprising: The apparatus comprises: A memory and a processor, which are connected in communication with each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the method of any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 1 to 6.

10. A computer program product, characterised in that, The computer readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 1 to 6. The computer readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 1 to 6.

Images