Design change-based heterogeneous system service collaboration method and device

Abstract

The invention relates to a heterogeneous system business collaboration method and device based on design change, the device comprises a data operation module, a judgment module, an external timing module and a trigger module, and the method comprises the following steps: changing data management and business logic of business collaboration according to the design; a design change business collaboration process is divided into three stages, namely a technical scheme stage, an information internal transmission stage and an information external transmission stage, and in different stages, in heterogeneous environments of different application systems and databases, relevant identifiers completed by closed loops or nodes of all stages set by the device are adopted to trigger to enter a subsequent business collaboration stage, so that the business collaboration efficiency is improved. And transmission of design change information among different application systems, different departments or external benefit parties is completed. According to the method and the system, design change information cross-department and information transmission with external benefit parties in a heterogeneous application system environment are realized, errors or delay possibly caused by manual operation is avoided, the product quality is improved, and the product cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a heterogeneous system business collaboration method and device based on design changes. Background Art

[0002] As enterprises carry out digital transformation, for various reasons, different business links adopt different information systems to meet different business needs, and these systems often use different database management systems.

[0003] Product design changes are a relatively complex process that has the greatest impact on product cost, quality, delivery time, and service. They are closely related to functional departments such as process engineering, procurement, manufacturing, installation, safety, and quality. After a design change occurs, it is necessary to determine the subsequent business status, such as whether the production list of the changed parts has been issued, whether they have been produced, installed, sold, shipped, and are within the warranty period. Only then can the product design change information be communicated to subsequent business-related departments according to different business workflows.

[0004] For such a complex business process, how to speed up the business collaboration process and avoid errors in the intermediate links are difficult problems that must be solved. Summary of the Invention

[0005] In order to speed up the flow of heterogeneous system business collaboration of the above-mentioned design change information and reduce possible errors or delays caused by manual operations in traditional ways, the present invention provides a heterogeneous system business collaboration method and device based on design changes to solve the product design change business, the information transmission between different application systems used in different stages, and the collaboration between various business departments and external stakeholders.

[0006] On the one hand, the present invention provides a heterogeneous system business collaboration method based on design change. The method divides the design change business collaboration process into the following steps based on the data management and business logic of the design change business collaboration:

[0007] Technical solution stage: This is the stage for planning and changing the technical solution to realize the design change within the technical department, using the first application system and the first database, involving the design department and its personnel;

[0008] Internal information transmission stage: To achieve cross-departmental business collaboration of design change information within the unit, the second application system and the second database are used, involving relevant departments and personnel within the unit;

[0009] External information transmission stage: In order to realize the transmission of design change information between the internal and external parties of the unit, a third-party application system and email system are used, involving relevant stakeholders and their personnel outside the unit.

[0010] Furthermore, the initiation and completion of each design change collaboration phase include:

[0011] The initiation of the technical solution phase is to start the compilation in the first application system, which is the initiation of the technical solution phase of the design change business collaboration; the end of the technical solution phase is to complete the editing-proofreading-review process of the design change in the first application system and mark it, which is the end of the technical solution phase of the design change business collaboration;

[0012] The initiation of the internal information transmission phase is marked with a design change completion flag in the first application system, which is the initiation of the internal information transmission phase of the design change business collaboration;

[0013] The internal information transmission phase ends when the processing of the process node related to the business unit in the second application system is completed and the process node completion identifier is written into the second database, which means that the internal information transmission phase of the design change business collaboration ends;

[0014] The initiation of the external information transmission phase is when the completion identifier of the process node of this business unit is written into the second database during the internal information transmission phase, which is the initiation of the external information transmission phase of the design change completion identifier; the end of the external information transmission phase is when the external parties receive the design change information in the third application system, which is the end of the external information transmission phase of the design change business collaboration.

[0015] Furthermore, the method further comprises:

[0016] In the technical solution phase, when a closed loop of the editing-proofreading-reviewing process is formed in the first application system and a design change completion mark is provided, the internal information transmission phase can be automatically or manually triggered;

[0017] During the internal information transmission phase, the design change business collaboration forms a closed loop in the second application system. In the second application system, a form and change attachments are used to implement the transmission or feedback of design change information based on the scope of the design change. When the processing of the process node of the business unit involved is completed, the external information transmission phase can be triggered automatically or manually.

[0018] During the external information transmission stage, the design change business collaboration forms a closed loop in the third application system, and the design change information is transmitted or fed back to external parties in the third application system by email according to the scope of the design change.

[0019] Furthermore, the internal information transmission stage also includes:

[0020] Data transfer: writing the design change information from the first database to the second database. When writing, first determine whether the design change information already exists in the second database. If it does exist, do not write it again.

[0021] File transfer: The technical solution attachments involving design changes saved in the product data management system will be uploaded to the folder in the specified path of the second application system. If the technical solution attachments already exist in the second database, they will not be uploaded again.

[0022] In another aspect, the present invention provides a heterogeneous system business collaboration device based on design changes for implementing the business collaboration method, comprising:

[0023] A data operation module performs data reading and writing operations between different application systems and different databases for the design change business collaboration; when the edit-proofread-review closed loop is achieved in the technical solution stage, a design change completion mark is marked in the first database; when the process node of the business unit involved in the internal information transmission stage is handled, a process node completion mark is marked in the second database;

[0024] a judgment module, configured to judge whether a closed loop has been achieved in the first application system during the technical solution phase, and to judge whether the processing of the process nodes of the business unit involved in the internal information transmission phase in the second application system has been completed;

[0025] An external timing module uses the timing operation instruction of the operating system to start the device at a set time point;

[0026] The trigger module triggers the start of the subsequent process of design change business collaboration through external instructions or the external timing module:

[0027] When the technical solution phase is closed, the design change information is triggered to be written from the first database to the second database, and the attachments involved in the first application system are imported into the folder specified by the second application system, and then the internal information transmission phase is started;

[0028] When the internal information transmission phase is completed in the second application system involving the process node of this business unit, the data and files of the design change information are exported from the second database and the folder specified by the second application system to the third application system, and the external information transmission phase is started.

[0029] Compared with the existing technology, the present invention realizes the information transmission of design change information across departments and with external stakeholders in a heterogeneous application system environment, avoids errors or delays that may be caused by manual operations, improves product quality and reduces product costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 It is a flowchart of a business collaboration method according to an embodiment of the present invention.

[0031] Figure 2 This is a structural block diagram of a business collaboration device and its data access according to an embodiment of the present invention. DETAILED DESCRIPTION

[0032] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0033] The present invention provides a heterogeneous system business collaboration method and device based on design changes, which are used in the product implementation process to realize the cross-departmental and information transmission of design change information and external stakeholders in a heterogeneous application system environment based on the data management and business logic of design change business collaboration, thereby reducing possible errors or delays caused by manual operations in traditional ways, thereby improving product quality and reducing product costs.

[0034] like Figure 1 As shown, the heterogeneous system service collaboration method includes the following steps:

[0035] Step S101: The technical solution for the design change is initiated by the designer in the first application system Aa. After a closed loop is formed by editing, proofreading and reviewing within the design department, the design change completion mark is written into the first database Ad S205, and serves as the basis for initiating the internal information transmission process, writing the design change information into the second application system Ba, importing the attachment S207 into the designated folder of the second application system Ba, and the subsequent process of design change business collaboration entering the second application system Ba.

[0036] Step S102: Initiate an internal information transmission process in the second application system Ba. After the processing of the business unit process node involved in the design change business collaboration is completed, write the completion identifier of the business unit process node into the second database BdS206, and use it as the basis for initiating an external information transmission process, importing the design change information and attachment S207 into the third application system Ca.

[0037] Step S103: After completing the processing of the business unit process node of the business collaboration, according to the completion mark of the business unit process node saved in the second database Bd in S206, the design change information and attachments are sent to the external stakeholders through the third application system Ca by email.

[0038] like Figure 2 As shown, the heterogeneous system service collaboration device includes:

[0039] External timing module S201: starts the data operation module S202, the judgment module S203 and the trigger module S204 at the expected time through the external instruction of the operating system to implement the steps S101, S102 and S103.

[0040] Data operation module S202: In step S101, when the editing-proofreading-reviewing process forms a closed loop within the design department, the technical solution stage closed loop flag in the first database Ad S205 is set to true; in step S102, when the process node of this business unit is completed, the completion flag of the process node of this business unit in the second database Bd S206 is set to true.

[0041] Judgment module S203: In step S101, the design change information whose technical solution stage closed-loop flag in the first database Ad S205 is set to true and does not exist in the second database Bd S206 is filtered out; in step S102, the design change information whose process node completion flag in the business unit is set to true in the second database Bd S206 and no email has been sent from the third application system Ca is filtered out.

[0042] Trigger module S204: In step S101, the design change information filtered by the judgment module S203 is written into the second database Bd S206, and the attachments in the first application system Aa are imported into the designated folder of the second application system Ba, triggering the second application system Ba to start the internal transmission of design change business collaboration information; in step S102, the design change information filtered by the judgment module S203 and the attachment S207 in the designated folder of the second application system Ba are output to the third application system Ca, triggering the sending of the design change information email, and setting the email sending flag in the second database Bd S206 to true, thereby realizing information transmission with external stakeholders without manual intervention and without duplication.

Claims

1. A heterogeneous system business collaboration method based on design changes, characterized by: The method divides the design change business collaboration process into the following parts based on the data management and business logic of the design change business collaboration: Technical solution stage: This is the stage for planning and changing the technical solution to realize the design change within the technical department, using the first application system and the first database, involving the design department and its personnel; Internal information transmission stage: To achieve cross-departmental business collaboration of design change information within the unit, the second application system and the second database are used, involving relevant departments and personnel within the unit; External information transmission stage: In order to realize the transmission of design change information between the internal and external parties of the unit, a third-party application system and email system are used, involving relevant stakeholders and their personnel outside the unit.

2. The heterogeneous system business collaboration method based on design change according to claim 1 is characterized in that: The initiation and completion of each design change collaboration phase include: The initiation of the technical solution phase is to start the compilation in the first application system, which is the initiation of the technical solution phase of the design change business collaboration; the end of the technical solution phase is to complete the editing-proofreading-review process of the design change in the first application system and mark it, which is the end of the technical solution phase of the design change business collaboration; The initiation of the internal information transmission phase is marked with a design change completion flag in the first application system, which is the initiation of the internal information transmission phase of the design change business collaboration; The internal information transmission phase ends when the processing of the process node related to the business unit in the second application system is completed and the process node completion identifier is written into the second database, which means that the internal information transmission phase of the design change business collaboration ends; The initiation of the external information transmission phase is when the completion identifier of the process node of this business unit is written into the second database during the internal information transmission phase, which is the initiation of the external information transmission phase of the design change completion identifier; the end of the external information transmission phase is when the external parties receive the design change information in the third application system, which is the end of the external information transmission phase of the design change business collaboration.

3. The heterogeneous system business collaboration method based on design change according to claim 2 is characterized in that: The method further comprises: In the technical solution phase, when a closed loop of the editing-proofreading-reviewing process is formed in the first application system and a design change completion mark is provided, the internal information transmission phase can be automatically or manually triggered; During the internal information transmission phase, the design change business collaboration forms a closed loop in the second application system. In the second application system, a form and change attachments are used to implement the transmission or feedback of design change information based on the scope of the design change. When the processing of the process node of the business unit involved is completed, the external information transmission phase can be triggered automatically or manually. During the external information transmission stage, the design change business collaboration forms a closed loop in the third application system, and the design change information is transmitted or fed back to external parties in the third application system by email according to the scope of the design change.

4. The heterogeneous system business collaboration method based on design change according to claim 3 is characterized in that: The internal information transmission stage also includes: Data transfer: writing the design change information from the first database to the second database. When writing, first determine whether the design change information already exists in the second database. If it does exist, do not write it again. File transfer: The technical solution attachments involving design changes saved in the product data management system will be uploaded to the folder in the specified path of the second application system. If the technical solution attachments already exist in the second database, they will not be uploaded again.

5. A device for implementing the heterogeneous system service collaboration method based on design changes as described in claim 1, characterized in that: The device comprises: A data operation module performs data reading and writing operations between different application systems and different databases for the design change business collaboration; when the edit-proofread-review closed loop is achieved in the technical solution stage, a design change completion mark is marked in the first database; when the process node of the business unit involved in the internal information transmission stage is handled, a process node completion mark is marked in the second database; a judgment module, configured to judge whether a closed loop has been achieved in the first application system during the technical solution phase, and to judge whether the processing of the process nodes of the business unit involved in the internal information transmission phase in the second application system has been completed; An external timing module uses the timing operation instruction of the operating system to start the device at a set time point; The trigger module triggers the start of the subsequent process of design change business collaboration through external instructions or the external timing module: When the technical solution phase is closed, the design change information is triggered to be written from the first database to the second database, and the attachments involved in the first application system are imported into the folder specified by the second application system, and then the internal information transmission phase is started; When the internal information transmission phase is completed in the second application system involving the process node of this business unit, the data and files of the design change information are exported from the second database and the folder specified by the second application system to the third application system, and the external information transmission phase is started.

Images