Engineering change closed-loop management method and device
By obtaining structured change notifications in rail transit equipment manufacturing and splitting them into tasks, the complex and cumbersome problems of engineering change management are solved, and the closed-loop management of changes and the improvement of product quality are achieved.
Patent Information
- Application Number
- CN202411405346.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-09
- Publication Date
- 2025-02-28
Smart Images
Figure CN119539826A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of rail transit equipment manufacturing, and provides a closed-loop management method and device for engineering changes. Background Art
[0002] In the manufacturing of rail transit equipment, etc., due to the characteristics of the products being produced with many models, frequent changes, and complicated change items, in order to ensure that the content of the engineering changes can be 100% executed on the corresponding products, the engineering changes are currently managed by manually recording them in ledgers. This method has the potential for omissions and errors, and is not convenient for tracing the entire change process and for closed-loop management of engineering changes. Summary of the invention
[0003] The embodiments of the present invention provide a closed-loop management method and device for engineering changes, which are used to solve the defects of engineering change management methods in related technologies, such as being complicated, difficult to execute, prone to errors, and difficult to trace, so as to achieve closed-loop management of the entire process of engineering changes and improve product quality.
[0004] The present invention provides a closed-loop management method for engineering changes, comprising: Obtaining a change notification in the rail transit equipment manufacturing process, wherein the change notification includes a number of structured change items; Based on the change notification, the engineering changes involved are divided into several notification tasks; The status of each notification task is confirmed, and based on the confirmation result, a corresponding task processing logic is executed, wherein the task processing logic is used to perform closed-loop management on each notification task.
[0005] According to the closed-loop management method for engineering changes provided by the present invention, the step of obtaining a change notification specifically includes: Set up structured change items according to the actual task requirements of the rail transit equipment manufacturing process; Allocating the content of the change notification to each of the change items; The change items include the content of the change notification, WBS elements, and the team that executes the change; the WBS elements are used to characterize the scope of the execution train.
[0006] According to the closed-loop management method for engineering changes provided by the present invention, based on the change notification, the steps of splitting the engineering changes involved into several notification tasks specifically include: Based on the change notification, the WBS element is decomposed into single-vehicle WBS elements; According to the notification change content, single vehicle WBS elements, and the team that executes the change in the change notification, the engineering changes involved are divided into several notification tasks.
[0007] According to the closed-loop management method for engineering changes provided by the present invention, the step of confirming the status of each notification task specifically includes: Distribute the notification tasks according to work groups; The current tasks assigned to each team are judged to determine the task status, wherein the task status includes tasks that can be executed by the team, tasks forwarded to other teams for execution, and abnormal tasks.
[0008] According to the closed-loop management method for engineering changes provided by the present invention, the steps of judging the current tasks assigned to each team and determining the task status specifically include: If the current task is executable by the team that dispatches the task, the current task is determined as an executable task for the team; If the current task is not executable by the team that dispatches the task, a second confirmation is performed on the current task; If the secondary confirmation result shows that the team that dispatches the task can execute it, the current task is determined as a task that can be executed by the team; If the secondary confirmation result shows that the team that assigned the task cannot execute it, then confirm whether it can be assigned to other teams for execution; If the confirmation result shows that the current task can be assigned to other teams for execution, the current task is assigned to other teams for execution, and the current task is determined as a task forwarded to other teams for execution; When the confirmation result is that the current task cannot be assigned to other teams for execution, the current task is determined as an abnormal task.
[0009] According to the closed-loop management method for engineering changes provided by the present invention, the steps of executing corresponding task processing logic based on the judgment result specifically include: When the current task is to forward the task to other teams for execution, the current task will be dispatched to other corresponding executable teams for execution; If the current task is executable by the team, execute the current task, and close the task after passing the execution; If the current task is an abnormal task, the change notification is confirmed. If it is confirmed that the change notification needs to be modified and re-executed, the change notification is modified and re-structured, task decomposed and task assigned; if it is confirmed that the change notification cannot be re-executed, the abnormal task is closed; After all notification tasks are closed, the change notification is closed.
[0010] According to the closed-loop management method for engineering changes provided by the present invention, when the current task is an executable task for the team, the steps for executing the current task specifically include: If the current task is executable by the team, the current task will be executed according to the change notification content and the execution content will be submitted for quality inspection; If the quality inspection result is qualified, the task is closed; if the quality inspection result is unqualified, the original team that executed the task returns to execute it again until it is qualified and the task is closed.
[0011] The present invention also provides an engineering change closed-loop management device, comprising the following modules: An acquisition module, used to acquire a change notification in the rail transit equipment manufacturing process, wherein the change notification includes a plurality of structured change items; A task splitting module, used to split the engineering changes involved into several notification tasks based on the change notification; The closed-loop module is used to confirm the status of each notification task and execute corresponding task processing logic based on the confirmation result. The task processing logic is used to perform closed-loop management on each notification task.
[0012] The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the closed-loop management method for engineering changes as described above is implemented.
[0013] The present invention also provides a non-transitory computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the closed-loop management method for engineering changes as described in any one of the above is implemented.
[0014] The present invention also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the closed-loop management method for engineering changes as described above is implemented.
[0015] The closed-loop management method and device for engineering changes provided by the present invention obtains change notifications in the manufacturing process of rail transit equipment, wherein the change notifications include several structured change items; based on the change notifications, the engineering changes involved are split into several notification tasks; the status of each notification task is confirmed, and based on the confirmation result, the corresponding task processing logic is executed, and the task processing logic is used to perform closed-loop management of each notification task. The present invention implements closed-loop management of the entire process of engineering changes by task-based control of the change execution content, solves the problems of large changes in rail transit vehicles and difficulty in tracing, ensures 100% execution of factory vehicle changes, and effectively improves product quality. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0017] Figure 1 It is a flow chart of the closed-loop management method for engineering changes provided by the present invention.
[0018] Figure 2 It is a schematic diagram of the structure of the structured change notification provided by the present invention.
[0019] Figure 3 This is the specific process of closed-loop management of engineering changes provided by the present invention.
[0020] Figure 4 It is a structural schematic diagram of the engineering change closed-loop management device provided by the present invention.
[0021] Figure 5 It is a structural schematic diagram of the electronic device provided by the present invention. DETAILED DESCRIPTION
[0022] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0023] The present invention is described in detail below in conjunction with the accompanying drawings of the specification. The specific operating method in the method embodiment can also be applied to the device embodiment or the system embodiment. In the description of the present invention, unless otherwise specified, "at least one" includes one or more. "Multiple" refers to two or more. For example, at least one of A, B and C includes: A exists alone, B exists alone, A and B exist at the same time, A and C exist at the same time, B and C exist at the same time, and A, B and C exist at the same time. In the present invention, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a kind of association relationship that describes the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.
[0024] The present invention will be described in detail below in conjunction with specific implementation modes.
[0025] In some specific embodiments of the present invention, Figure 1 As shown, this solution provides a closed-loop management method for engineering changes, which includes the following steps: Step 100: Obtain a change notification in the rail transit equipment manufacturing process, wherein the change notification includes a plurality of structured change items; Step 200: Based on the change notification, split the engineering change involved into a number of notification tasks; Step 300: confirm the status of each notification task, and execute corresponding task processing logic based on the confirmation result, wherein the task processing logic is used to perform closed-loop management on each notification task.
[0026] It should be noted that the existing engineering change management solution for rail transit equipment manufacturing cannot fully implement the engineering change content of the entire product life cycle, and can only be managed by manual record keeping. The operation is cumbersome, and there are omissions and errors. It is not easy to trace the entire change process, and it is impossible to ensure 100% implementation of changes for factory vehicles.
[0027] Therefore, the present invention obtains a change notification, which includes several structured change items, splits the engineering changes involved into several notification tasks according to the change notification, and realizes change management of the engineering changes by closed-loop management of each notification task. By managing and controlling the change execution content in a task-based manner, a closed loop of the entire engineering change process is achieved, which solves the problems of large changes in rail transit vehicles and difficult traceability, ensures 100% execution of changes in factory vehicles, and effectively improves product quality.
[0028] In some possible implementations of the present invention, the step of obtaining the change notification specifically includes: Set up structured change items according to the actual task requirements of the rail transit equipment manufacturing process; Allocating the content of the change notification to each of the change items; The change items include the content of the change notification, WBS elements, and the team that executes the change; the WBS elements are used to characterize the scope of the execution train.
[0029] Specifically, this embodiment provides an implementation method for obtaining a structured change notification, by presetting change items, structuring the content of the change notification, and decomposing different change tasks according to the content of the change items.
[0030] In a possible embodiment, if Figure 2 As shown, Figure 2A schematic diagram of the structure of a structured change notification is shown. The content of the change notification is structured. A notification consists of several change items. Each change may include: the content of the notification change, the scope of the execution list (i.e., WBS elements), the team that executes the change, and other key contents.
[0031] Specifically, Figure 2 Change Notice A in the above example can be in different forms before structured processing, such as introducing the team that will perform the change first, then describing the content of the change, and finally providing the range of vehicles involved in the change, etc. Change Notice B can first introduce the content of the change, then provide the range of vehicles involved in the change, and finally describe the team that will perform the change, etc. This recording method is extremely complicated for the rail transit equipment manufacturing process. Due to the characteristics of rail transit equipment manufacturing, such as many models of products, frequent changes, and complicated change items, it is difficult to ensure that the engineering change content can be 100% executed on the corresponding products.
[0032] By processing the change notification in a specific order of the change items, after obtaining the change notification after structured processing, the specific content of each change item involved in the change notification can be directly and quickly known, so that the engineering change content involved in the change notification can be quickly classified and tasked. At the same time, the change items can be specifically set according to the actual task requirements of the rail transit equipment manufacturing process, such as the change characteristics, production mode, and control requirements of rail transit vehicles. Compared with the traditional engineering change processing method, it is more flexible and scientific, providing convenient conditions for the subsequent task splitting of engineering changes, and to a certain extent improving the execution quality of product changes.
[0033] Furthermore, after the structured change notification is edited, the change notification needs to be reviewed and released.
[0034] In some possible implementations of the present invention, based on the change notification, the steps of splitting the engineering change involved into several notification tasks specifically include: Based on the change notification, the WBS element is decomposed into single-vehicle WBS elements; According to the notification change content, single vehicle WBS elements, and the team that executes the change in the change notification, the engineering changes involved are divided into several notification tasks.
[0035] Specifically, this embodiment provides an implementation method for splitting an engineering change into several notification tasks, by splitting the scope WBS element of the execution column into single-vehicle WBS elements, and decomposing the engineering changes involved in the change notification according to the content of the split change items.
[0036] In a possible embodiment, if the WBS element in the change notification is such as GT-C084.P.(001~100).(01~08), it is used to indicate that the change content GT-C084 involves trains P001 to P100, and the execution teams are teams 01-08. The change content can be divided into different single-vehicle WBS elements according to the single vehicle, such as GT-C084.P.001.01, which is used to represent that the change content GT-C084 involves train P001 and is executed by team 01.
[0037] On this basis, according to the content of the disassembled change items, such as change notification content, single vehicle WBS elements, execution team, etc., the engineering changes involved in the change notification are decomposed into different notification tasks.
[0038] In some possible implementations of the present invention, the step of confirming the status of each notification task specifically includes: Distribute the notification tasks according to work groups; The current tasks assigned to each team are judged to determine the task status, wherein the task status includes tasks that can be executed by the team, tasks forwarded to other teams for execution, and abnormal tasks.
[0039] Specifically, this embodiment provides an implementation method for closed-loop management of notification tasks, by distributing the decomposed notification content and executing the corresponding task processing logic according to the status of the dispatched tasks.
[0040] In some possible implementations of the present invention, the step of judging the current tasks assigned to each team and determining the task status specifically includes: If the current task is executable by the team that dispatches the task, the current task is determined as an executable task for the team; If the current task is not executable by the team that dispatches the task, a second confirmation is performed on the current task; If the secondary confirmation result shows that the team that dispatches the task can execute it, the current task is determined as a task that can be executed by the team; If the secondary confirmation result shows that the team that assigned the task cannot execute it, then confirm whether it can be assigned to other teams for execution; If the confirmation result shows that the current task can be assigned to other teams for execution, the current task is assigned to other teams for execution, and the current task is determined as a task forwarded to other teams for execution; When the confirmation result is that the current task cannot be assigned to other teams for execution, the current task is determined as an abnormal task.
[0041] Specifically, this embodiment provides an implementation method for determining the task status, by judging whether the task is executable and determining the task status according to the judgment result.
[0042] In a possible embodiment, the disassembled tasks are distributed according to work groups. After receiving the execution tasks, the work groups confirm whether the tasks can be executed. If they can be executed, the tasks are accepted. If they cannot be executed, the reasons need to be explained and abnormal task feedback is provided.
[0043] Furthermore, after the execution task is assigned to the team, if the team determines that it cannot be executed, it is necessary to explain the specific reasons for the inability to execute, and then submit the task as an abnormal task for process confirmation. After process confirmation, if it is considered that the team can execute it, the submission will be rejected. If it is considered that it cannot be executed, it will be determined whether it can be assigned to other teams for execution. If it is determined that it can be assigned to a new team for execution, the original team task will be recovered and assigned to a new team, and then it will be assigned again. If it cannot be assigned to a new team for execution, the task will be determined as an abnormal task and the abnormal task will be closed.
[0044] In some possible implementations of the present invention, based on the judgment result, the steps of executing the corresponding task processing logic specifically include: When the current task is to forward the task to other teams for execution, the current task will be dispatched to other corresponding executable teams for execution; If the current task is executable by the team, execute the current task, and close the task after passing the execution; If the current task is an abnormal task, the change notification is confirmed. If it is confirmed that the change notification needs to be modified and re-executed, the change notification is modified and re-structured, task decomposed and task assigned; if it is confirmed that the change notification cannot be re-executed, the abnormal task is closed; After all notification tasks are closed, the change notification is closed.
[0045] Specifically, this embodiment provides an implementation method for executing corresponding task processing logic, by judging the task status and executing different task processing logics according to different task statuses.
[0046] In a possible embodiment, for tasks that need to be forwarded to other teams for execution, the system recovers them from the original team and dispatches them to the executable team for execution; each team needs to execute the tasks that can be executed by the team according to the content of the change notification, and close the task after the execution is qualified; In a possible embodiment, for tasks judged to be abnormal, it is necessary to further confirm whether the change notification needs to be modified and re-executed. If so, the change notification is modified, and the content of the change notification is re-structured based on the modified change notification. Then, the engineering changes involved in the change notification are subjected to task decomposition, task dispatch, task execution and other procedures. If it is confirmed that the change notification cannot be re-executed after modification, or cannot be modified, or there are other problems that cannot be solved by modification, the task is closed.
[0047] After all the decomposed notification tasks are closed, all the tasks that can be executed are completed, and when all the tasks that need to be closed are closed, the change notification is executed and closed.
[0048] In some possible implementations of the present invention, when the current task is an executable task for the team, the steps of executing the current task specifically include: If the current task is executable by the team, the current task will be executed according to the change notification content and the execution content will be submitted for quality inspection; If the quality inspection result is qualified, the task is closed; if the quality inspection result is unqualified, the original team that executed the task returns to execute it again until it is qualified and the task is closed.
[0049] Specifically, this embodiment provides an implementation method for each team to execute the executable tasks of the team according to the content of the change notification, and completes the execution of the notified task by executing and quality inspecting the executable tasks and passing the quality inspection.
[0050] The closed-loop management method for engineering changes provided in the embodiments of the present invention combines the change characteristics, production mode, and control requirements of rail transit vehicles, and implements closed-loop management of the entire process of engineering changes from the source to production execution, quality inspection, abnormal feedback and processing by task-based control of change execution content. It solves the management difficulties such as the large number of changes and difficult traceability of rail transit vehicles, ensures 100% execution of factory vehicle changes, and effectively improves product quality.
[0051] In some specific embodiments of the present invention, Figure 3 As shown, this solution provides a specific process for closed-loop management of engineering changes. The implementation process of the present invention mainly consists of two parts: structuring of change notifications and closed-loop management of change notifications.
[0052] Specifically, regarding the structuring of change notifications: Before structuring the change notification, it is necessary to conduct an impact analysis of the change, modify the product data according to the impact analysis structure, and then prepare a structured change notification based on this.
[0053] The content of the change notification is structured. A notification consists of several change items. Each change includes: the content of the notification change, the scope of the execution list (i.e. WBS elements), the team that executes the change, and other key contents. After the structured notification is edited, the change notification is reviewed and released.
[0054] Closed-loop management of change notifications, including: Step 1: Notification task decomposition
[0055] In this step, based on the structured notification, the WBS element range is decomposed into single-vehicle WBS (for example: GT-C084.P.001.01) according to the WBS element vehicle range (for example: GT-C084.P.(001~100).(01~08)), and then it is split into several notification tasks according to the change notification content, single-vehicle WBS element, and execution team.
[0056] Step 2: Notify task dispatch
[0057] After decomposing the engineering changes involved in the change notice, the decomposed tasks will be assigned to the work groups. After receiving the execution tasks, the work groups will confirm whether the tasks can be executed. If they can be executed, they will accept the tasks and execute the received notification tasks. If they cannot be executed, they need to explain the reasons and provide abnormal task feedback.
[0058] Step 3: Notify task execution
[0059] The team will execute the executable tasks according to the contents of the change notification. After completion, they will select quality inspection personnel to report that the task has been executed. The next step is for the quality inspection personnel to check and confirm the execution content. If the inspection is qualified, the task will be closed. If the inspection is unqualified, it will be returned to the team to execute again until the execution is qualified.
[0060] Step 4: Abnormal task handling
[0061] After the execution task is assigned to the team, if the team cannot execute it, explain the reason and submit the task as an abnormal task for process confirmation. After process confirmation, if the team is deemed to be executable, the submission will be rejected. If it is deemed not executable, it will be determined whether it can be assigned to other teams for execution. If it can be assigned to a new team, the original team task will be recovered and assigned to a new team, and then reassigned. If it cannot be assigned to a new team, the abnormal task will be closed. For abnormally closed tasks, it is necessary to confirm whether the content needs to be modified and re-executed. If so, the modified new change notification will be issued and returned to the structured change notification preparation stage to re-execute the subsequent process; if not, the abnormal closed status will be maintained.
[0062] Step 5. Close the change notification
[0063] After all notification tasks obtained by decomposition are closed, it means that all notification tasks have been executed. In this case, the change notification is closed, and product delivery can be carried out subsequently. The status of the engineering changes involved in the change notification can be statistically analyzed and the status of the change notification can be updated.
[0064] It can be seen from the specific process of closed-loop management of engineering changes provided by the embodiment of the present invention that the closed-loop management method of engineering changes provided by the embodiment of the present invention is essentially a task-driven full-process management method for engineering changes. By dividing the execution content into tasks according to key elements, dispatching engineering change execution tasks, feedback on the execution of tasks, checking tasks and handling abnormal tasks, combined with the change characteristics and production mode of rail transit vehicles, the full-process closed-loop management of engineering changes of rail transit vehicles is implemented, and closed-loop management of changes in the whole process from changes in product design source to change execution, change inspection and confirmation, and abnormal change feedback processing in subsequent production and manufacturing is realized. The whole process of engineering change execution can be clearly tracked, the integrity of change execution can be managed, and vehicle quality problems caused by failure to implement changes can be avoided.
[0065] The engineering change closed-loop management device provided by the present invention is described below. The engineering change closed-loop management device described below and the engineering change closed-loop management method described above can be referenced to each other.
[0066] In some specific embodiments of the present invention, Figure 4 As shown, this solution provides an engineering change closed-loop management device for rail transit equipment manufacturing, including: An acquisition module 41 is used to acquire structured change notifications, wherein each of the change notifications includes a number of change items; A task splitting module 42 is used to split the engineering change involved into a plurality of notification tasks based on the change notification; The closed-loop module 43 is used to perform closed-loop management on each notification task.
[0067] Optionally, the step of obtaining the change notification specifically includes: Set up structured change items according to the actual task requirements of the rail transit equipment manufacturing process; Allocating the content of the change notification to each of the change items; The change items include the content of the change notification, WBS elements, and the team that executes the change; the WBS elements are used to characterize the scope of the execution train.
[0068] Specifically, this embodiment provides an implementation method for obtaining a change notification.
[0069] Optionally, based on the change notification, the steps of dividing the engineering change involved into several notification tasks specifically include: Based on the change notification, the WBS element is decomposed into single-vehicle WBS elements; According to the notification change content, single vehicle WBS elements, and the team that executes the change in the change notification, the engineering changes involved are divided into several notification tasks.
[0070] Specifically, this embodiment provides an implementation method for splitting an engineering change into several notification tasks.
[0071] Optionally, the step of confirming the status of each notification task specifically includes: Distribute the notification tasks according to work groups; The current tasks assigned to each team are judged to determine the task status, wherein the task status includes tasks that can be executed by the team, tasks forwarded to other teams for execution, and abnormal tasks.
[0072] Specifically, this embodiment provides an implementation method for confirming the status of each notification task.
[0073] Optionally, the step of judging the current tasks assigned to each team and determining the task status specifically includes: If the current task is executable by the team that dispatches the task, the current task is determined as an executable task for the team; If the current task is not executable by the team that dispatches the task, a second confirmation is performed on the current task; If the secondary confirmation result shows that the team that dispatches the task can execute it, the current task is determined as a task that can be executed by the team; If the secondary confirmation result shows that the team that assigned the task cannot execute it, then confirm whether it can be assigned to other teams for execution; If the confirmation result shows that the current task can be assigned to other teams for execution, the current task is assigned to other teams for execution, and the current task is determined as a task forwarded to other teams for execution; When the confirmation result is that the current task cannot be assigned to other teams for execution, the current task is determined as an abnormal task.
[0074] Specifically, this embodiment provides an implementation method for determining a task status.
[0075] Optionally, based on the judgment result, the steps of executing corresponding task processing logic specifically include: When the current task is to forward the task to other teams for execution, the current task will be dispatched to other corresponding executable teams for execution; If the current task is executable by the team, execute the current task. After the task is executed successfully, close the task. If the current task is an abnormal task, the change notification is confirmed. If it is confirmed that the change notification needs to be modified and re-executed, the change notification is modified and re-structured, task decomposed and task assigned; if it is confirmed that the change notification cannot be re-executed, the abnormal task is closed; After all notification tasks are closed, the change notification is closed.
[0076] Specifically, this embodiment provides an implementation method for executing corresponding task processing logic.
[0077] Optionally, when the current task is an executable task for the team, the steps for executing the current task specifically include: If the current task is executable by the team, the current task will be executed according to the change notification content and the execution content will be submitted for quality inspection; If the quality inspection result is qualified, the task is closed; if the quality inspection result is unqualified, the original team that executed the task will return to execute it again until it is qualified and the task is closed.
[0078] Specifically, this embodiment provides an implementation method for executing the current task.
[0079] The implementation principle and beneficial effects of the closed-loop management device for engineering changes provided in the embodiment of the present invention are similar to the implementation principle and beneficial effects of the closed-loop management method for engineering changes shown in the above embodiment. Please refer to the implementation principle and beneficial effects of the closed-loop management method for engineering changes shown in the above embodiment, and no further details will be given here.
[0080] Figure 5 An example of a physical structure diagram of an electronic device is shown in FIG. Figure 5As shown, the electronic device may include: a processor 510, a communication interface 520, a memory 530 and a communication bus 540, wherein the processor 510, the communication interface 520 and the memory 530 communicate with each other through the communication bus 540. The processor 510 may call the logic instructions in the memory 530 to execute the closed-loop management method for engineering changes, the method comprising: obtaining a structured change notification, wherein each of the change notifications includes a plurality of change items; based on the change notifications, splitting the engineering changes involved into a plurality of notification tasks; and performing closed-loop management on each of the notification tasks.
[0081] In addition, the logic instructions in the above-mentioned memory 530 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.
[0082] On the other hand, the present invention also provides a computer program product, which includes a computer program. The computer program can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the closed-loop management method of engineering changes provided by the above methods, the method including: obtaining a structured change notification, wherein each of the change notifications includes a number of change items; based on the change notifications, splitting the engineering changes involved into a number of notification tasks; and performing closed-loop management of each of the notification tasks.
[0083] On the other hand, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, it is implemented to execute the closed-loop management method of engineering changes provided by the above-mentioned methods, the method comprising: obtaining a structured change notification, wherein each of the change notifications includes a number of change items; based on the change notifications, splitting the engineering changes involved into a number of notification tasks; and performing closed-loop management of each of the notification tasks.
[0084] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.
[0085] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0086] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A closed-loop management method for engineering changes, characterized in that: include: Obtaining a change notification in the rail transit equipment manufacturing process, wherein the change notification includes a number of structured change items; Based on the change notification, the engineering changes involved are divided into several notification tasks; The status of each notification task is confirmed, and based on the confirmation result, a corresponding task processing logic is executed, wherein the task processing logic is used to perform closed-loop management on each notification task.
2. The closed-loop management method for engineering changes according to claim 1, characterized in that: The steps to obtain change notifications include: Set up structured change items according to the actual task requirements of the rail transit equipment manufacturing process; Allocating the content of the change notification to each of the change items; The change items include the content of the change notification, WBS elements, and the team that executes the change; the WBS elements are used to characterize the scope of the execution train.
3. The closed-loop management method for engineering changes according to claim 2 is characterized in that: Based on the change notification, the engineering changes involved are divided into several notification task steps, including: Based on the change notification, the WBS element is decomposed into single-vehicle WBS elements; According to the notification change content, single vehicle WBS elements, and the team that executes the change in the change notification, the engineering changes involved are divided into several notification tasks.
4. The closed-loop management method for engineering changes according to any one of claims 1 to 3, characterized in that: The step of confirming the status of each notification task specifically includes: Distribute the notification tasks according to work groups; The current tasks assigned to each team are judged to determine the task status, wherein the task status includes tasks that can be executed by the team, tasks forwarded to other teams for execution, and abnormal tasks.
5. The closed-loop management method for engineering changes according to claim 4 is characterized in that: The steps to judge the current tasks assigned to each team and determine the task status include: If the current task is executable by the team that dispatches the task, the current task is determined as an executable task for the team; If the current task is not executable by the team that dispatches the task, a second confirmation is performed on the current task; If the secondary confirmation result shows that the team that dispatches the task can execute it, the current task is determined as a task that can be executed by the team; If the secondary confirmation result shows that the team that assigned the task cannot execute it, then confirm whether it can be assigned to other teams for execution; If the confirmation result shows that the current task can be assigned to other teams for execution, the current task is assigned to other teams for execution, and the current task is determined as a task forwarded to other teams for execution; When the confirmation result is that the current task cannot be assigned to other teams for execution, the current task is determined as an abnormal task.
6. The closed-loop management method for engineering changes according to claim 5, characterized in that: Based on the judgment result, the steps of executing the corresponding task processing logic include: When the current task is to forward the task to other teams for execution, the current task will be dispatched to other corresponding executable teams for execution; If the current task is executable by the team, execute the current task. After the task is executed successfully, close the task. If the current task is an abnormal task, the change notification is confirmed. If it is confirmed that the change notification needs to be modified and re-executed, the change notification is modified and re-structured, task decomposed and task assigned; if it is confirmed that the change notification cannot be re-executed, the abnormal task is closed; After all notification tasks are closed, the change notification is closed.
7. The closed-loop management method for engineering changes according to claim 6, characterized in that: When the current task is executable by the team, the steps for executing the current task include: If the current task is executable by the team, the current task will be executed according to the change notification content and the execution content will be submitted for quality inspection; If the quality inspection result is qualified, the task is closed; if the quality inspection result is unqualified, the original team that executed the task returns to execute it again until it is qualified and the task is closed.
8. A closed-loop management device for engineering changes, characterized in that: include: An acquisition module, used to acquire a change notification in the rail transit equipment manufacturing process, wherein the change notification includes a plurality of structured change items; A task splitting module, used to split the engineering changes involved into several notification tasks based on the change notification; The closed-loop module is used to confirm the status of each notification task and execute corresponding task processing logic based on the confirmation result. The task processing logic is used to perform closed-loop management on each notification task.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the closed-loop management method for engineering changes as described in any one of claims 1 to 7 is implemented.
10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the closed-loop management method for engineering changes as described in any one of claims 1 to 7 is implemented.