Mutual lifting condition generation method and system and computer device

Abstract

The application discloses a mutual submission condition generation method and system and a computer device, and is applied to the technical field of data processing. The method comprises the following steps: in response to the selection operation of a target project stage and a submitter profession of a submitter, determining a target mutual submission condition template matched with the target project stage and the submitter profession from a mutual submission condition template library. A dynamic form rendering engine is called, and a parameter input interface is generated and displayed according to the target mutual submission condition template. In response to the confirmation operation of the submitter on the input parameters in the parameter input interface, a target mutual submission condition is generated based on the input parameters, and at least one receiver profession and a receiver responsible person of each receiver profession are determined based on the target mutual submission condition template. A mutual submission condition notice including the target mutual submission condition is generated, and the mutual submission condition notice is sent to a business system associated with each receiver responsible person. The embodiment of the application can realize accurate generation of the mutual submission condition notice.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, system and computer device for generating mutual extraction conditions. Background Technology

[0002] Large-scale engineering design projects, such as mining engineering, power engineering, and chemical engineering, typically involve multiple disciplines including geology, mining, mineral processing, and civil engineering, with numerous complex data dependencies between these disciplines. To ensure consistency and traceability in cross-disciplinary design collaboration, it is necessary to standardize the handover process of technical parameters, attached figures, and tables from each discipline by creating mutual transfer condition notices, thereby ensuring the orderly and efficient progress of engineering design projects.

[0003] Therefore, how to automate the generation of mutual condition notification forms to improve design collaboration efficiency and finished product delivery quality has become an urgent problem to be solved. Summary of the Invention

[0004] In view of this, embodiments of this application provide a method, system, and computer device for generating mutual extraction conditions, which can realize the automated generation of mutual extraction condition notifications, thereby improving design collaboration efficiency and finished product delivery quality.

[0005] Firstly, this application provides a method for generating mutual extraction conditions, including: In response to the selection of the target project stage and the proposer's expertise by the proposer's personnel, the target mutual extraction condition template that matches the target project stage and the proposer's expertise is determined from the pre-built mutual extraction condition template library. Call the dynamic form rendering engine to generate and display the parameter input interface according to the structured configuration of predefined text items, image items and table items in the target mutual extraction condition template; In response to the confirmation operation of the proposer's personnel on the parameter input interface, the target mutual extraction conditions are generated based on the text parameters, attached figures and tables included in the input parameters. Based on the predefined professional mapping relationship in the target mutual extraction condition template, at least one receiving professional and the receiving person in charge of each receiving professional are determined. Generate a mutual transfer condition notification that includes the target mutual transfer conditions, and send the mutual transfer condition notification to the business system associated with the professional receiving manager of each receiving party.

[0006] Secondly, this application provides another method for generating mutual extraction conditions, including: Receive the mutual submission condition notification sent by the business system associated with the submitting party; According to the preset condition verification rules, the target mutual conditions included in the mutual condition notification are verified to obtain the condition verification results; wherein, the preset condition verification rules include at least one of the following: condition content completeness verification, condition data rationality verification, and design requirement compliance verification. If the verification results indicate that the mutual transfer conditions have passed the verification, the mutual transfer conditions will be archived in the receiving condition directory corresponding to the receiving party's major.

[0007] Thirdly, this application provides a mutual transfer condition generation system, including a proposing device and at least one receiving device, wherein the proposing device is used to execute the mutual transfer condition generation method of the first aspect described above, and the receiving device is used to execute the mutual transfer condition generation method of the second aspect described above.

[0008] Fourthly, this application provides a storage medium on which a computer program is stored, which, when executed by a processor, implements the above-described method for generating mutual extraction conditions.

[0009] Fifthly, this application provides a computer device, which includes a proposing device and at least one receiving device, comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the program to implement the above-described method for generating mutual extraction conditions.

[0010] By utilizing the above technical solutions, the mutual transfer condition generation method, system, and computer equipment provided in this application, in response to the selection operation of the target project stage and the proposing party's profession, match the corresponding target mutual transfer condition template, and call a dynamic form rendering engine to generate a parameter input interface based on the structured configuration of the template. This can adapt to the mutual transfer condition input needs of different project stages and different professions, eliminating the need to develop separate pages for various scenarios and reducing system development and maintenance costs. Furthermore, after receiving the confirmation operation of the input parameters, the target mutual transfer conditions are automatically generated based on the input text parameters, attached figures, and attached tables. The receiving party's profession and the receiving person in charge are automatically determined based on the predefined professional mapping relationship of the template, reducing matching deviations caused by manual judgment. A mutual transfer condition notification containing the target mutual transfer conditions is then automatically generated and pushed to the business system associated with the corresponding receiving person in charge. This automates the processing of mutual transfer conditions from template matching, parameter input, condition generation to notification distribution, reducing the workload of manual editing and reducing the risk of missing or incorrect parameters and incorrect matching of transfer objects. This improves the accuracy, standardization, and collaborative flow efficiency of design data handover between multiple professions in large-scale projects.

[0011] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0012] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This illustration shows a schematic diagram of the structure of a cross-extraction condition generation system provided in an embodiment of this application; Figure 2 A flowchart illustrating a method for generating mutual extraction conditions provided in an embodiment of this application is shown. Figure 3 A flowchart illustrating another method for generating mutual extraction conditions provided in an embodiment of this application is shown. Detailed Implementation

[0013] To facilitate the explanation of the embodiments of this application, some technical terms and technical means related to the embodiments of this application, as well as the application scenarios of the embodiments of this application, will be introduced first below.

[0014] In some cases, the proposing party can send the mutual transfer conditions to the receiving party using a paper notification. Specifically, the proposing party manually prepares the mutual transfer condition notification, including textual descriptions and parameter tables, which is then signed and reviewed by the relevant professional leader and delivered to the receiving party in paper form. It is only put into use after the receiving party signs for receipt and confirmation. However, because the formats of mutual transfer condition notifications prepared by different proposing parties vary and there is a lack of a unified template, key technical parameters or necessary attachments are easily omitted, leading to repeated communication and supplementation, increasing coordination costs. Furthermore, since all technical parameters involved in the mutual transfer condition notification rely on manual filling and calculation, problems such as numerical errors, unit errors, and data inconsistencies are prone to occur, and these errors are difficult to detect and correct during the filling stage. In addition, paper approval not only requires the transmission of physical documents at each level, resulting in a long approval cycle and low process transparency, but also means that the approver's business trip can directly cause process interruptions. Moreover, the document relies on manual delivery, which carries the risk of omissions or incorrect delivery, making it difficult for the receiving party to obtain the mutual transfer conditions in a timely manner, seriously affecting the overall progress of the engineering design project.

[0015] In other cases, the proposing party can send the mutual submission conditions to the receiving party via email or shared folders. Specifically, the proposing party uses common office software such as Word and Excel to generate the mutual submission condition notification form, and then sends it to the receiving party via email, or uploads it to the project's shared folder for the receiving party to download. Since the approval process still primarily relies on offline paper signatures or email confirmations, while this method digitizes the sending method, the preparation of the mutual submission condition notification form still depends on manual completion using common office software, resulting in inconsistent formatting and missing content. Furthermore, because emails are stored in a decentralized manner, there is a lack of a unified view for managing mutual submission conditions, making it difficult to quickly retrieve and trace historical condition records. Moreover, version management of the mutual submission condition notification form is challenging; multiple versions of the document, resulting from numerous revisions, are scattered across various emails and folders, easily leading to version confusion and ultimately affecting the overall quality of the engineering design project.

[0016] In some other cases, the proposer can use general project management platforms such as office automation (OA) systems and building information modeling (BIM) collaboration platforms to manage the mutual submission of conditions as ordinary document tasks. They can use the document sending and receiving and task assignment functions of the general project management platform to complete the transfer of condition documents, and use the process approval function built into the general project management platform to conduct condition review. However, this general project management platform has not been customized for the business characteristics of mutual condition notifications. It lacks dedicated functions such as professional templates, professional interface constraints, and condition integrity verification. It does not have a professional template library for mutual condition notifications, and cannot automatically match standardized condition templates according to different project stages and professional combinations. It also lacks the ability to enforce validation of mandatory fields based on industry knowledge, making it difficult to automatically verify the integrity of the condition content. Furthermore, it lacks the ability to constrain professional interfaces, and cannot automatically identify and match the correspondence between the proposing and receiving professional fields of the mutual condition. It also lacks the ability to visualize the panoramic progress of mutual condition, and cannot intuitively display the status of all mutual condition in a professional-professional matrix format. Moreover, document archiving is disconnected from business processes, and it cannot automatically archive documents to the corresponding professional directory after the condition is submitted.

[0017] Therefore, to achieve accurate generation of cross-subject exchange condition notifications and improve design collaboration efficiency and product delivery quality, this application provides a cross-subject exchange condition generation method. In this method, in response to the requester's selection of the target project stage and the requester's specialty, a target cross-subject exchange condition template matching the target project stage and the requester's specialty is determined from a pre-built cross-subject exchange condition template library. Then, a dynamic form rendering engine is invoked to generate and display a parameter input interface according to the structured configuration of predefined text items, attached figure items, and attached table items in the target cross-subject exchange condition template. In response to the requester's confirmation of the parameters entered in the parameter input interface, target cross-subject exchange conditions are generated based on the text parameters, attached figures, and attached tables included in the entered parameters. Based on the predefined specialty mapping relationships in the target cross-subject exchange condition template, at least one receiving specialty and the receiving manager for each receiving specialty are determined. Finally, a cross-subject exchange condition notification including the target cross-subject exchange conditions is generated and sent to the business systems associated with the receiving managers of each receiving specialty.

[0018] Among them, the above-mentioned mutual transfer conditions are a collection of technical data provided by the proposing party to the receiving party in engineering design projects involving multiple disciplines such as mining, power, and chemical engineering. This collection of data is used by the receiving party to carry out the design work. It includes design input information such as textual parameters, drawings, and tables, and serves as the technical basis for design handover between different disciplines.

[0019] In this embodiment, by responding to the selection operation of the target project stage and the proposing party's profession, matching the corresponding target mutual transfer condition template, and calling the dynamic form rendering engine to generate a parameter input interface based on the structured configuration of the template, it can adapt to the mutual transfer condition input needs of different project stages and different professions, without the need to develop separate pages for various scenarios, thus reducing system development and maintenance costs. Furthermore, after receiving the confirmation operation of the input parameters, the target mutual transfer conditions are automatically generated based on the input text parameters, attached figures, and attached tables. The receiving party's profession and the receiving person in charge are automatically determined based on the professional mapping relationship predefined in the template, reducing matching deviations caused by manual judgment. Then, a mutual transfer condition notification containing the target mutual transfer conditions is automatically generated and pushed to the business system associated with the corresponding receiving person in charge. This automates the processing of mutual transfer conditions from template matching, parameter input, condition generation to notification distribution, reducing the workload of manual editing and reducing the risk of missing or incorrect parameters and incorrect matching of transfer objects. This improves the accuracy, standardization, and collaborative flow efficiency of design data handover between multiple professions in large-scale projects.

[0020] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the embodiments of the present application can be combined with each other.

[0021] like Figure 1 As shown in the illustration, this application provides a cross-platform condition generation system, including: a proposing device 110 and at least one receiving device 120. The proposing device refers to a computer device used by the proposing personnel to access their associated business system. The receiving device refers to a computer device used by the receiving professional's responsible person to access their associated business system. The receiving professional is the receiving professional corresponding to the proposing personnel's proposing professional in the professional mapping relationship.

[0022] In some cases, the proposing device 110 may include a template matching module 111, an interface display module 112, and a condition generation module 113. The template matching module 111 is used to determine a target mutual extraction condition template that matches the target project stage and the proposing party's expertise from a pre-built mutual extraction condition template library.

[0023] The aforementioned mutual transfer condition template library can include multiple mutual transfer condition templates, as well as corresponding project stages, text content templates, figure templates, table templates, and professional mapping relationships for each template. Text content templates define at least one text item required for mutual transfer conditions, along with mandatory or optional attributes for each text item. Each text item includes a project number, text title, a text description including parameter placeholders, and the associated set of receiving party professions. Figure templates define the types, number, and naming conventions of figures required for mutual transfer conditions. For example, figure types could be ore body layout maps, mining completion plans, etc. Table templates define the types, table structures, and data fields of tables required for mutual transfer conditions. For example, table types could be ore resource summary tables, mining and stripping schedule tables, etc. The aforementioned professional mapping relationships define the correspondence between the proposing and receiving professions to which the mutual transfer condition templates apply. In other words, professional mapping relationships characterize the mapping relationship between the proposing and receiving professions. For example, if the proposing profession is mining, the receiving profession could be geology, hydrogeology, etc.

[0024] The aforementioned interface display module 112 is used to call the dynamic form rendering engine to generate and display the parameter input interface according to the structured configuration of predefined text items, image items, and table items in the target mutual extraction condition template. The parameter input interface includes at least parameter input boxes for text items, image upload areas for image items, and table upload areas for table items. Correspondingly, the parameter input interface may also include an online editing area, which can be used for online editing of either tables or images; the specific choice is not limited.

[0025] The aforementioned condition generation module 113 is used to generate target mutual transfer conditions and send a mutual transfer condition notification, including the target mutual transfer conditions, to the receiving device. Specifically, upon receiving confirmation from the requesting party regarding the parameters entered in the parameter input interface, the condition generation module 113 can generate target mutual transfer conditions based on the text parameters, attached figures, and tables included in the entered parameters. Simultaneously, the condition generation module 113 can determine at least one receiving specialty and the receiving manager for each receiving specialty based on the predefined professional mapping relationships in the target mutual transfer condition template. Afterward, the condition generation module 113 can generate a mutual transfer condition notification including the target mutual transfer conditions and send the mutual transfer condition notification to the receiving device of the corresponding receiving manager for each receiving specialty.

[0026] In other cases, the receiving device 120 may include a condition verification module 121 and a condition archiving module 122. The condition verification module 121 verifies the target mutual transfer conditions included in the mutual transfer condition notification according to preset condition verification rules, and obtains the condition verification result. The preset condition verification rules include at least one of the following: condition content completeness verification, condition data rationality verification, and design requirement compliance verification. The condition verification result indicates whether the target mutual transfer conditions have passed verification.

[0027] The aforementioned condition archiving module 122 is used to archive the target mutual extraction conditions to the receiving condition directory corresponding to the recipient's major. Specifically, if the condition verification result indicates that the target mutual extraction conditions have passed the verification, the condition archiving module 122 can archive the target mutual extraction conditions to the receiving condition directory corresponding to the recipient's major.

[0028] In some embodiments, such as Figure 1 As shown, in response to the submitter's selection of the target project stage and submitter's expertise, the submitter device 110 can trigger the template matching module 111 to determine the target mutual transfer condition template matching the target project stage and submitter's expertise from a pre-built mutual transfer condition template library. Then, the template matching module 111 can execute step a, sending the target mutual transfer condition template to the interface display module 112 and the condition generation module 113. Upon receiving the target mutual transfer condition template sent by the template matching module 111, the interface display module 112 calls the dynamic form rendering engine to generate and display the parameter input interface according to the structured configuration of predefined text items, figure items, and table items in the target mutual transfer condition template. Then, in response to the submitter's confirmation of the parameters entered in the parameter input interface, the interface display module 112 can obtain the input parameters including text parameters, figure items, and table items, and execute step b, sending the input parameters to the condition generation module 113.

[0029] Accordingly, upon receiving the target mutual transfer condition template sent by the template matching module 111, the condition generation module 113 determines at least one receiving specialty and the receiving manager for each receiving specialty based on the predefined professional mapping relationship in the target mutual transfer condition template. Upon receiving the input parameters sent by the interface display module 112, the condition generation module 113 generates target mutual transfer conditions based on the input parameters, thereby generating a mutual transfer condition notification that includes the target mutual transfer conditions. Afterwards, the condition generation module 113 can execute step c, sending the mutual transfer condition notification to the condition verification module 121 of the receiving device 120 corresponding to the receiving manager of each receiving specialty.

[0030] Upon receiving a mutual transfer condition notification from the condition generation module 113 of the proposing device 110, the condition verification module 121 of the receiving device 120 verifies the target mutual transfer conditions included in the notification according to preset condition verification rules, and obtains the condition verification result. If the condition verification result indicates that the target mutual transfer conditions have passed verification, the condition verification module 121 can execute step d, sending the target mutual transfer conditions to the condition archiving module 122. Upon receiving the target mutual transfer conditions sent by the condition verification module 121, the condition archiving module 122 archives the target mutual transfer conditions to the receiving device's professional receiving condition directory.

[0031] Furthermore, this embodiment provides a method for generating mutual extraction conditions, such as... Figure 2 As shown, the method includes: S2001, the proposing party's equipment receives the proposing party's personnel's selection and operation based on the target project stage and the proposing party's expertise.

[0032] The "proposing party's equipment" refers to the computer equipment used by the proposing party's personnel to access their associated business systems. The target project stage can be the pre-feasibility study stage, feasibility study stage, or preliminary design stage, etc. The proposing party's professional background can be in design fields such as geology, hydrogeology, mining, civil engineering, geotechnical engineering, mining machinery, mineral processing, general layout, HVAC, electrical engineering, information and control, digital engineering, or technical economics.

[0033] S2002, the proposing device determines the target mutual extraction condition template that matches the target project stage and the proposing device's expertise from the pre-built mutual extraction condition template library.

[0034] Specifically, after receiving the selection of the target project stage and the proposer's specialty from the submitter's personnel, a target mutual transfer condition template matching the target project stage and the proposer's specialty can be determined from a pre-built mutual transfer condition template library. This mutual transfer condition template library can include multiple mutual transfer condition templates, along with corresponding project stages, text content templates, figure templates, appendix templates, and specialty mapping relationships for each template. Figure templates define the types and number of figures required for the mutual transfer conditions, as well as naming conventions. For example, figure types could be ore body layout maps or mining completion plans. Appendix templates define the types, table structures, and data fields required for the mutual transfer conditions. For example, appendix types could be ore resource summary tables or mining and stripping schedule tables.

[0035] The aforementioned text content template defines at least one text item required for cross-exchange conditions, along with mandatory or optional attributes for each item. Each text item includes an item number, a text title, a text description including parameter placeholders, and the associated set of receiving party specialties. The aforementioned specialty mapping relationship defines the correspondence between the proposing and receiving specialties to which the cross-exchange condition template applies. In other words, the specialty mapping relationship characterizes the mapping relationship between the proposing and receiving specialties. For example, if the proposing specialty is mining, the receiving specialty could be geology, hydrogeology, etc.

[0036] For example, as shown in Table 1, the text content template corresponding to the mutual transfer condition template can include seven text items: mine scale, work system, service life, ore body geological model, physical and mechanical properties of ore and rock, open-pit mining design optimization parameters, and comprehensive utilization rate. Among them, the item number corresponding to mine scale is WZ01, and the text content description can include the annual production scale of the open-pit mine, the daily production scale of the open-pit mine, the mining area, the coordinates of the mining area, the annual production capacity, and the daily production capacity. The receiving professional set corresponding to mine scale can include geology, hydrogeology, civil engineering, geotechnical engineering, mining machinery, mineral processing, electrical engineering, general layout, and cataloging. The item number corresponding to work system is WZ02, and the text content description can include the number of working days per year, the total number of shifts per day, and the working hours of each shift. The receiving professional set corresponding to work system can include hydrogeology, geology, civil engineering, geotechnical engineering, mining machinery, mineral processing, and HVAC. The project number corresponding to the service period is WZ03. The textual description of the service period may include the service period, the service period of the first phase of the mining area, and the service period of the second phase of the mining area. The professional set of the receiving party corresponding to the service period may include civil engineering, geotechnical engineering, geology, hydrogeology, mining machinery, mineral processing, and HVAC.

[0037] The project number corresponding to the above-mentioned ore body geological model is WZ04. The textual description of the ore body geological model may include bench height, requirements for the ore body geological model, and specific requirements for ore type and ore grade classification. The receiving professional set for the ore body geological model may include hydrogeology, geology, and technical economics. The project number corresponding to the above-mentioned ore and rock physical and mechanical properties is WZ05. The textual description of the above-mentioned ore and rock physical and mechanical properties may include ore bulk density, ore and rock loosening coefficient, ore and rock f-value coefficient, ore and rock water content, and ore and rock mud content. The receiving professional set for the above-mentioned ore and rock physical and mechanical properties may include civil engineering, mining machinery, mineral processing, general layout, and mining planning. The project number corresponding to the above-mentioned open-pit mining design optimization parameters is WZ06. The textual description of the above-mentioned open-pit mining design optimization parameters may include the final slope angle of the open-pit mine, the minimum mining elevation of the open-pit mine, the slope of the transportation road, the bench slope angle, and the number of parallel sections. The receiving professional set for the above-mentioned open-pit mining design optimization parameters may include geotechnical engineering, mining machinery, general layout, environmental protection, and energy conservation. The project number corresponding to the comprehensive utilization rate is WZ07. The textual description of the comprehensive utilization rate can include mineral processing recovery rate and metal loss rate. The professional set of the receiving parties corresponding to the comprehensive utilization rate can include mineral processing professionals, technical economic professionals, and engineering cost professionals.

[0038] Table 1. List of text content templates corresponding to the mutual sharing condition templates

[0039] Furthermore, after determining the aforementioned target exchange condition template, the condition processing status can be updated to the pending creation status. In some embodiments of this application, the condition processing status can be divided into pending creation status, approval status, pending sending status, sent status, received status, and archived status.

[0040] S2003, the proposing device calls the dynamic form rendering engine to generate and display the parameter input interface according to the structured configuration of predefined text items, figure items and table items in the target mutual extraction condition template.

[0041] Specifically, after determining the aforementioned target exchange condition template, a dynamic form rendering engine can be invoked to render the data according to the predefined structured configuration of text items, image items, and table items in the target exchange condition template, thereby generating and displaying the parameter input interface. The parameter input interface includes at least parameter input boxes for text items, image upload areas for image items, and table upload areas for table items. The parameter input boxes can be text boxes, numeric boxes, dropdown selection boxes, etc. Correspondingly, the parameter input interface may also include an online editing area, which can be used for online editing of tables or images, without specific limitations.

[0042] S2004, The proposing device receives confirmation from the proposing personnel regarding the parameters entered in the parameter input interface.

[0043] Specifically, after the parameter input interface is displayed, the receiving party confirms the parameters entered in the interface. These parameters may include text parameters, attached figures, and tables.

[0044] In one implementation, in response to the submitter's input of parameters into the parameter input box, the parameters are validated according to preset parameter validation rules to obtain a text validation result. The preset parameter validation rules include at least one of the following: mandatory field validation, data type validation, and consistency validation of associated parameters. The parameter validation result indicates whether the parameters submitted by the submitter have passed validation.

[0045] In some embodiments, if the parameter verification result indicates that the parameters entered by the submitter have passed verification, then the parameters entered by the submitter are determined as the input parameters. This allows for automatic parameter verification during the parameter input stage, promptly identifying issues such as missing required fields, incorrect data types, and logical inconsistencies in related parameters. It filters out unqualified parameters at the source, reducing the workload of manual item-by-item verification, and preventing erroneous or missing parameters from flowing into the subsequent mutual extraction condition generation stage. This effectively improves the completeness and accuracy of the input parameters and ensures the data reliability of the subsequently generated mutual extraction conditions and mutual extraction condition notifications.

[0046] For example, taking the mine scale projects included in Table 1 above as an example, the input parameters can be determined as 1.2 million tons per year for the annual production scale of open-pit mine, 1.2 million tons per day for the daily production scale of open-pit mine, 150 cubic kilometers for the area of ​​mine, and 1.21 million tons per year for the annual production capacity.

[0047] In other embodiments, if the parameter verification result indicates that the parameter entered by the submitting personnel failed verification, a first prompt message is output to inform the submitting personnel of the reason for the parameter failure. Subsequently, in response to the submitting personnel's parameter modification operation, the modified parameters are re-verified according to preset parameter verification rules until the modified parameters pass verification, at which point the modified parameters are confirmed as input parameters. This achieves closed-loop parameter verification and correction, guiding users to complete parameter rectification, preventing defective parameters from directly entering subsequent business processes, further ensuring the integrity and accuracy of input parameters, reducing the probability of data errors when generating mutual extraction conditions and mutual extraction condition notifications, and improving the reliability of multi-disciplinary engineering design data mutual extraction.

[0048] In another implementation, in response to the submitter's upload of an attached drawing in the attached drawing upload area, the uploaded drawing is checked according to preset attached drawing verification rules to obtain a verification result. These preset attached drawing verification rules include at least one of the following: attached drawing format compliance verification, attached drawing size compliance verification, attached drawing type matching verification, attached drawing and text parameter consistency verification, and professional relevance verification. Attached drawing size compliance verification checks whether the file size of the uploaded attached drawing is within a preset range. Attached drawing type matching verification checks whether the drawing type of the uploaded attached drawing matches the attached drawing type required by the aforementioned target mutual transfer condition template. Attached drawing and text parameter consistency verification checks whether the content recorded in the attached drawing is consistent with the text parameters manually entered by the submitter. Professional relevance verification checks whether the uploaded attached drawing is compatible with the submitter's profession and the business requirements of the target project stage. The attached drawing verification result indicates whether the attached drawing uploaded by the submitter passes the verification.

[0049] In some embodiments, if the attached drawing verification result indicates that the attached drawing uploaded by the submitting party has passed verification, the attached drawing uploaded by the submitting party is determined as the input parameter. This allows for automatic verification of attached drawings during the input stage, promptly identifying aspects such as file format, file size, drawing type, text-image matching relationship, and professional relevance. This fundamentally prevents unqualified attached drawings from entering subsequent processing, reduces the workload of manual attached drawing review, ensures the standardization and effectiveness of the input attached drawings, and ultimately improves the overall data quality of the subsequently generated mutual submission conditions and mutual submission condition notifications.

[0050] In other embodiments, if the attached drawing verification result indicates that the attached drawing uploaded by the submitting party has failed verification, a second prompt message is output to inform the submitting party of the reason for the failure. Subsequently, in response to the attached drawing upload operation in the submitting party's attached drawing upload area, the attached drawing uploaded by the submitting party is re-verified according to preset attached drawing verification rules until the uploaded attached drawing passes verification. Only then is the verified attached drawing determined as an input parameter. This achieves closed-loop verification and correction of attached drawings, guiding users to complete attached drawing rectification, preventing defective attached drawings from directly entering subsequent business processes, further ensuring the integrity and accuracy of the entered attached drawings, reducing the probability of data errors when generating mutual extraction conditions and mutual extraction condition notifications, and improving the reliability of mutual extraction of multi-disciplinary engineering design data.

[0051] In another implementation, in response to the submitter's upload of an appendix to the appendix upload area, the appendix uploaded by the submitter is checked according to preset appendix verification rules to obtain an appendix verification result. The preset appendix verification rules include at least one of the following: appendix format compliance verification, appendix size compliance verification, header compliance verification, data type and format verification, numerical range verification, appendix type matching verification, appendix and text parameter consistency verification, and professional applicability verification. The appendix verification result indicates whether the appendix uploaded by the submitter passes the verification.

[0052] In some embodiments, if the appendix uploaded by the submitter passes the verification, the appendix is ​​designated as the input parameter. This allows for automatic appendix verification during the input stage, promptly identifying aspects such as appendix file format, file size, data type and format, numerical range, text-table matching relationships, and professional relevance. This fundamentally prevents unqualified appendix files from entering subsequent processing, reduces the workload of manual appendix review, ensures the standardization and effectiveness of entered appendixes, and ultimately improves the overall data quality of subsequently generated mutual extraction conditions and mutual extraction condition notifications.

[0053] In other embodiments, if the appendix verification result indicates that the appendix uploaded by the submitter has failed verification, a third prompt message is output to inform the submitter of the reason for the failure. Subsequently, in response to the appendix upload operation in the submitter's appendix upload area, the appendix uploaded by the submitter is re-verified according to preset appendix verification rules until it passes verification. Only then is the verified appendix confirmed as an input parameter. This achieves closed-loop verification and correction of appendices, guiding users to complete appendix rectification, preventing defective appendices from directly entering subsequent business processes, further ensuring the integrity and accuracy of entered appendices, reducing the probability of data errors when generating mutual extraction conditions and mutual extraction condition notifications, and improving the reliability of multi-disciplinary engineering design data mutual extraction.

[0054] S2005, the proposing device generates target mutual extraction conditions based on the text parameters, attached figures and tables included in the input parameters.

[0055] Specifically, after the above data entry operation is completed, if the receiving party confirms the data entry parameters, target exchange conditions can be generated based on the text parameters, attached figures, and attached tables included in the data entry parameters. In other words, these target exchange conditions include text parameters, attached figures, and attached tables. Furthermore, these target exchange conditions carry a corresponding identifier.

[0056] Furthermore, after generating the aforementioned target mutual extraction conditions, these conditions can be archived in the extraction condition directory corresponding to the proposing party's specialty. This allows for centralized classification and storage of the target mutual extraction conditions generated by the proposing party's specialty, facilitating unified review, version management, and historical tracing of the extraction conditions output by the proposing party. It also reduces the probability of lost extraction condition files and improves the standardization of engineering design business data management on the proposing party's side.

[0057] S2006, the proposing device determines at least one receiving specialty and the receiving person in charge of each receiving specialty based on the predefined professional mapping relationship in the target mutual extraction condition template.

[0058] Specifically, a professional interface constraint matrix is ​​established based on the predefined professional mapping relationships in the target mutual exchange condition template. The rows of the professional interface constraint matrix correspond to the proposing professional field, and the columns correspond to the receiving professional field. Each cell of the professional interface constraint matrix displays the condition status information between the proposing and receiving professional fields. The condition status information can include condition creation status, condition submission time or last update time, condition processing status, and condition processing status. Condition creation status indicates whether the target mutual exchange conditions have been successfully created. Condition processing status indicates whether there are any delays or overdue indicators for the target mutual exchange conditions.

[0059] Furthermore, after establishing the professional interface constraint matrix, at least one receiving professional that matches the proposing professional can be directly obtained from the matrix, and the receiving person in charge of each receiving professional can be identified. This not only enables a matrix-based centralized display of the interaction status of mutual conditions between different professional groups, but also allows for the rapid retrieval of the matching receiving professional group and its responsible person directly from the professional interface constraint matrix. This eliminates the tedious manual process of sorting and matching professional relationships, facilitating project managers to intuitively grasp the progress of mutual conditions across all professional groups, promptly identify delays and overdue issues, and improve the efficiency and process control capabilities of mutual condition matching during multi-professional collaborative design.

[0060] In one implementation, after generating the aforementioned target mutual transfer conditions, these conditions can be approved first. Only when the target mutual transfer conditions are approved can at least one receiving specialty and the responsible person for receiving each receiving specialty be determined based on the predefined professional mapping relationships in the target mutual transfer condition template. This allows for pre-approval of the mutual transfer conditions before they are pushed out, preventing unapproved mutual transfer conditions from being directly transferred to the receiving specialty. This reduces design rework caused by the transmission of erroneous or unreasonable technical data to downstream specialties, ensures the compliance and reliability of the externally output mutual transfer conditions, and improves the rigor and standardization of data handover during multi-disciplinary collaborative design processes.

[0061] Specifically, in response to the submitter's approval trigger for the target mutual exchange conditions, the conditions are approved, an approval result is obtained, and the condition processing status is changed from "pending" to "under approval." The approval result indicates whether the target mutual exchange conditions have passed approval. If the approval result indicates that the target mutual exchange conditions have passed approval, based on the predefined professional mapping relationships in the target mutual exchange condition template, at least one receiving specialty and the receiving manager for each receiving specialty are identified.

[0062] Correspondingly, if the condition for mutual exchange fails to pass the approval process, the condition is modified based on the feedback from the approval node. Upon completion of the modification, the modified condition is re-approved until it passes the final approval. This closed-loop mechanism of approval-modification-re-review ensures that modification feedback is fully incorporated into the approval process, promptly correcting any issues and preventing defective conditions from entering subsequent distribution stages. This guarantees the quality of exported mutual exchange conditions, reduces the risk of rework due to incorrect conditions received by downstream professionals, and further enhances the rigor and reliability of multi-disciplinary data exchange in large-scale projects.

[0063] In some cases, multiple approval nodes can be set up to approve the aforementioned target mutual submission conditions. In some embodiments of this application, the multiple approval nodes can be divided into preliminary review nodes, secondary review nodes, and final review nodes. The preliminary review node can be a node for approval by a key technical expert, the secondary review node can be a node for approval by the professional manager, and the final review node can be a node for approval by the project design manager. That is, in response to the confirmation operation of the key technical expert regarding the target mutual submission conditions, the target mutual submission conditions can be sent to the business system of the professional manager, triggering the secondary review node. Then, in response to the confirmation operation of the professional manager regarding the target mutual submission conditions, the target mutual submission conditions can be sent to the business system of the project design manager, triggering the final review node. Finally, in response to the confirmation operation of the project design manager regarding the target mutual submission conditions, a condition approval result indicating that the target mutual submission conditions have been approved can be obtained, and the condition processing status can be changed from "under approval" to "pending submission".

[0064] Correspondingly, in response to any approval node's return operation regarding the target mutual submission conditions, a condition modification suggestion is generated and sent to the business system of the proposing party. This allows the proposing party to modify the target mutual submission conditions according to the suggestion until the modified conditions pass through the aforementioned multiple approval nodes. This achieves a closed-loop process of approval return, suggestion issuance, and modification re-review, avoiding deviations in opinion transmission caused by verbal communication, clarifying the basis for modification, reducing repeated communication costs, ensuring the accuracy of mutual submission condition modification direction, and improving the overall approval workflow efficiency and the quality of engineering mutual submission condition preparation.

[0065] Optionally, in response to any approver's forwarding operation for the target mutual condition at any approval node, the personnel selected by the approver to be forwarded to are determined. Then, the approval node is forwarded to the business system of the personnel to be forwarded to, where they will review the information. This breaks through the limitations of fixed approval chains and allows for the flexible introduction of relevant personnel to participate in the review process for mutual condition approval scenarios involving cross-professional and cross-positional consultation and verification needs. This improves the approval process, helps avoid oversights caused by the limited knowledge coverage of a single approver, and enhances the comprehensiveness and reliability of the mutual condition approval results.

[0066] It is understandable that approval information is recorded simultaneously at each approval stage. This approval information may include the approver's name, approval time, and approval comments.

[0067] In other cases, the conditions for mutual exchange can also be approved according to preset approval rules. These preset approval rules may include at least one of the following: parameter accuracy approval rules, content completeness and reasonableness approval rules, and external release approval rules. The parameter accuracy approval rules verify the accuracy of each parameter in the mutual exchange conditions; the content completeness and reasonableness approval rules verify the completeness and reasonableness of the mutual exchange conditions; and the external release approval rules determine whether the mutual exchange conditions are permitted to be submitted externally.

[0068] S2007, The proposing device generates a mutual transfer condition notification that includes the target mutual transfer conditions.

[0069] Specifically, after obtaining the approval result for the target mutual transfer conditions, a mutual transfer condition notification can be generated based on the target mutual transfer conditions. This notification includes at least the textual parameters, attached figures, and appendices corresponding to the target mutual transfer conditions. Correspondingly, the notification may also include the project number, project name and / or project title, the proposing party's specialty, the name of the organization to which the proposing party's personnel belong, the identifier and version number of the target mutual transfer conditions, the submission date, and the name of the proposing party's personnel.

[0070] S2008, the proposing device sends a mutual proposal condition notification to the receiving device.

[0071] Specifically, after generating the aforementioned mutual transfer condition notification, the proposing device can send the mutual transfer condition notification to the receiving device and change the condition processing status from pending to sent to sent. Here, the receiving device refers to the computer device used by the designated personnel of each of the aforementioned receiving parties to access their associated business systems.

[0072] S2009: Upon receiving the mutual transfer condition notification sent by the proposing device, the receiving device verifies the target mutual transfer conditions included in the mutual transfer condition notification according to the preset condition verification rules, and obtains the condition verification result.

[0073] Specifically, after receiving the mutual extraction condition notification from the proposing device, the receiving device can verify the target mutual extraction conditions included in the notification according to preset condition verification rules, and adjust the condition processing status from sent to received. The preset condition verification rules include at least one of the following: condition content completeness verification, condition data rationality verification, and design requirement compliance verification.

[0074] In some cases, after receiving a mutual transfer condition notification from the sending device, the receiving device can also output a prompt message to remind the person in charge to promptly review and process the notification. This allows for timely reminders to the person in charge, preventing delays in processing mutual transfer conditions due to missed messages, ensuring timely responses to the handover of technical data between disciplines, and improving the efficiency of collaborative workflow in engineering design.

[0075] Furthermore, in response to the receiving manager's online viewing of the target exchange conditions, the receiving device can directly display the target exchange conditions to achieve an online preview function. Alternatively, in response to the receiving manager's offline viewing of the target exchange conditions, the receiving device can download the target exchange conditions document.

[0076] S2010, if the condition verification result indicates that the target mutual extraction conditions have passed the verification, the receiving device will archive the target mutual extraction conditions to the receiving condition directory corresponding to the receiving specialty.

[0077] Specifically, after receiving the verification results indicating that the target exchange conditions have passed verification, the receiving device can archive the target exchange conditions to the receiving professional's corresponding receiving condition directory and change the condition processing status from "received" to "archived". This enables targeted and categorized storage of exchange conditions, facilitating unified management and rapid retrieval of verified target exchange conditions by the receiving professional. It also ensures the orderly retention of exchange condition data, facilitating subsequent project traceability and improving the standardization of engineering design data management.

[0078] In some cases, the above-mentioned condition verification results can also indicate that the target exchange conditions have failed verification. Furthermore, after obtaining the condition verification results indicating that the target exchange conditions have failed verification, the receiving device can generate a problem list and remind the proposing party to modify the conditions. Specifically, such as... Figure 3 As shown, the method for generating mutual extraction conditions may also include S2011~S2017: S2011, if the condition verification result indicates that the mutual exchange conditions of the target have failed the verification, the receiving device generates a problem list.

[0079] Specifically, after obtaining the verification results of the conditions for mutual extraction of target representations that failed the verification, a problem list can be generated. This problem list can include the reasons why the mutual extraction conditions failed the verification and / or suggested modifications.

[0080] S2012, The receiving device sends a list of issues to the proposing device.

[0081] S2013, upon receiving a problem list from the receiving device, the proposing device, in response to the proposing personnel's condition change operation for the target mutual exchange conditions, modifies the target mutual exchange conditions.

[0082] Specifically, after receiving the problem list sent by the receiving device, if the proposing device detects a condition change operation by the proposing personnel regarding the target mutual exchange conditions, it can modify the target mutual exchange conditions based on that condition change operation.

[0083] S2014, in response to the completion of the target mutual transfer condition change, the proposing device approves the changed target mutual transfer condition until the condition approval result indicates that the target mutual transfer condition has been approved, and generates a new mutual transfer condition notification based on the changed target mutual transfer condition.

[0084] Specifically, after the aforementioned target exchange conditions are changed, the proposing device can re-approval the changed target exchange conditions until the approval result indicates that the target exchange conditions have passed. A new exchange condition notification is then generated based on the changed target exchange conditions. This ensures that the changed exchange conditions undergo compliance verification, avoids the direct distribution of unapproved changes to the recipient, prevents technical information errors caused by condition changes, guarantees the accuracy and business effectiveness of the changed exchange condition notification, and achieves a closed-loop business process of changing exchange conditions, re-approving, and issuing a new notification, ensuring the rigor of condition changes during multi-disciplinary engineering design collaboration.

[0085] It should be noted that the condition change process for the above target mutual transfer conditions can be executed at any step after the target mutual transfer conditions are generated. That is, steps S2013 to S2014 can be executed after step S2005, and the specific timing of execution is not limited.

[0086] S2015, the proposing device sends a condition change notification to the receiving device.

[0087] Specifically, after generating a new mutual transfer condition notification, the proposing device can send a condition change notification to the receiving device. This condition change notification specifies the location and details of any changes to the target mutual transfer conditions.

[0088] S2016, when the receiving device receives a condition change notification from the proposing device, it reviews the changes to the target mutual extraction conditions marked in the condition change notification based on the issue list, and obtains the condition review result.

[0089] Specifically, after receiving the condition change notification from the proposing device, the changes to the target mutual transfer conditions marked in the notification can be reviewed based on the aforementioned issue list to obtain a condition review result. This condition review result indicates whether the changes to the target mutual transfer conditions have passed verification.

[0090] In some embodiments, if the condition review result indicates that the changes to the target mutual transfer conditions have passed verification, it means that the changed target mutual transfer conditions comply with the preset condition verification rules. Therefore, the receiving device can execute step S2017 to archive the changed target mutual transfer conditions into the receiving condition directory corresponding to the receiving device's specialty. However, if the condition review result indicates that the changes to the target mutual transfer conditions have failed verification, it means that the changed target mutual transfer conditions still do not comply with the preset condition verification rules. Therefore, the receiving device can return to step S2011 until a condition review result indicating that the changes to the target mutual transfer conditions have passed verification is obtained, before archiving the changed target mutual transfer conditions into the receiving condition directory corresponding to the receiving device's specialty.

[0091] In some cases, after receiving a condition change notification from the proposing device, the receiving device can save the changed location and content of the target mutual transfer condition marked in the condition change notification, along with the aforementioned issue list, as supplementary information of the target mutual transfer condition. This allows for the complete retention of change details and related issue records of the mutual transfer condition, achieving linked storage of change information and original mutual transfer conditions. This facilitates the receiving personnel's intuitive understanding of condition changes, while also enabling data traceability and verification throughout the project lifecycle, preventing the loss of scattered change records, and further improving the integrity and traceability of collaborative engineering design data.

[0092] S2017, if the verification results indicate that the changes to the target mutual transfer conditions have passed the verification, the receiving device will archive the changed target mutual transfer conditions to the receiving condition directory corresponding to the receiving device's specialty.

[0093] Specifically, after receiving the verification results of the changed content representing the target mutual extraction conditions, the receiving device can archive the changed target mutual extraction conditions to the receiving condition directory corresponding to the receiving specialty. This allows for targeted archiving and retention of verified changed versions of mutual extraction conditions, achieving orderly management of mutual extraction condition versions before and after the change. This facilitates the receiving specialty's quick retrieval of the latest version of the mutual extraction conditions, while also enabling version traceability and data verification in later stages of the project, ensuring the integrity and traceability of change data during engineering design collaboration.

[0094] In some cases, after receiving the verification results of the changes to the target exchange conditions, the receiving device can also update the version number of the target exchange conditions and change the condition processing status from received to archived.

[0095] This application also provides a computer device, which includes a proposing device and at least one receiving device. Specifically, it can be a personal computer, server, network device, etc. The computer device includes a bus, processor, memory, and communication interface, and may also include input / output interfaces and a display device. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device stores location information. The network interface of the computer device is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements the steps in the various method embodiments.

[0096] Those skilled in the art will understand that the structure of the computer device described above is only a partial structure related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. A specific computer device may include more or fewer components, or combine certain components, or have different component arrangements.

[0097] In one embodiment, a computer-readable storage medium is provided, which may be non-volatile or volatile, having stored thereon a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0098] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0099] It should be noted that the user personal information involved in the embodiments of this application is all authorized (with the knowledge and consent) by the relevant parties or fully authorized by all parties, and the executing entity can obtain it through various legal and compliant means. The collection, storage, use, processing, transmission, provision, and disclosure of the information, data, and signals involved all comply with the relevant laws and regulations of the relevant countries and regions, and do not violate public order and good morals. It should be noted that if any software tools or components other than those of this company appear in the embodiments of this application, they are merely illustrative examples and do not represent actual use.

[0100] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0101] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0102] The embodiments described above are merely examples of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these modifications and improvements all fall within the protection scope of this application.

Claims

1. A method for generating mutual extraction conditions, characterized in that, Applied to the proposing device, the method includes: In response to the selection operation of the proposer's personnel regarding the target project stage and the proposer's expertise, a target mutual extraction condition template matching the target project stage and the proposer's expertise is determined from a pre-built mutual extraction condition template library. The dynamic form rendering engine is invoked to generate and display the parameter input interface according to the structured configuration of the predefined text items, image items, and table items in the target mutual extraction condition template; In response to the confirmation operation of the personnel of the proposing party regarding the parameters entered in the parameter input interface, target mutual extraction conditions are generated based on the text parameters, attached figures and tables included in the entered parameters, and at least one receiving party's profession and the receiving person in charge of each receiving party's profession are determined based on the predefined professional mapping relationship in the target mutual extraction condition template. Generate a mutual transfer condition notification that includes the target mutual transfer conditions, and send the mutual transfer condition notification to the business system associated with the receiving manager of each of the receiving parties.

2. The method according to claim 1, characterized in that, The step of determining at least one receiving major and the receiving manager for each receiving major based on the predefined professional mapping relationship in the target mutual transfer condition template includes: Based on the predefined professional mapping relationship in the target mutual extraction condition template, a professional interface constraint matrix is ​​established; wherein, the row dimension of the professional interface constraint matrix corresponds to the proposing party's professional field, and the column dimension corresponds to the receiving party's professional field. Obtain at least one receiving profession that matches the proposing profession from the professional interface constraint matrix, and determine the receiving person in charge for each of the receiving professions.

3. The method according to claim 1, characterized in that, The process of generating target cross-promotion conditions based on the text parameters, attached figures, and tables included in the input parameters, and determining at least one receiving specialty and the receiving manager for each of the receiving specialty based on the predefined professional mapping relationships in the target cross-promotion condition template, includes: Based on the text parameters, attached figures, and attached tables included in the input parameters, the target mutual extraction conditions are generated; In response to the approval trigger operation of the proposing party for the target mutual transfer conditions, the target mutual transfer conditions are approved, and the condition approval result is obtained; If the approval result indicates that the target mutual transfer conditions have been approved, the at least one receiving party major and the receiving person in charge of each receiving party major are determined based on the predefined professional mapping relationship in the target mutual transfer conditions template.

4. The method according to claim 3, characterized in that, The method further includes: If the condition approval result indicates that the target mutual transfer condition has not passed the approval, the target mutual transfer condition shall be modified based on the condition modification opinions fed back by the approval node. In response to the completion of the modification of the target mutual transfer conditions, the modified target mutual transfer conditions are re-approved until the approval result indicates that the target mutual transfer conditions have passed the approval.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: In response to the condition change operation of the proposing party regarding the target mutual exchange conditions, the target mutual exchange conditions are changed; In response to the completion of the target mutual transfer condition change, the changed target mutual transfer condition is approved until the condition approval result indicates that the target mutual transfer condition has been approved, and a new mutual transfer condition notification is generated based on the changed target mutual transfer condition. Send a condition change notification to the business system associated with the professional receiving manager of the at least one recipient; wherein the condition change notification indicates the location and content of the change in the target mutual exchange conditions.

6. The method according to any one of claims 1-4, characterized in that, When the parameter input interface includes a parameter input box corresponding to the text item, an image upload area corresponding to the image item, and an appendix upload area corresponding to the appendix item, the method further includes: In response to the parameter input operation of the submitting party, the parameters entered by the submitting party are validated according to the preset parameter validation rules to obtain a text validation result. If the parameter validation result indicates that the parameters entered by the submitting party have passed the validation, the parameters entered by the submitting party are determined as the input parameters. The preset parameter validation rules include at least one of the following: mandatory field validation, data type validation, and consistency validation of related parameters. In response to the submission personnel's upload operation of an attached image in the attached image upload area, the uploaded image is checked according to preset attached image verification rules to obtain an attached image verification result. If the attached image verification result indicates that the uploaded image has passed the verification, the uploaded image is determined as the input parameter. The preset attached image verification rules include at least one of the following: attached image format compliance verification, attached image size compliance verification, attached image type matching verification, attached image and text parameter consistency verification, and professional relevance verification. In response to the submitter's upload operation of the appendix in the appendix upload area, the appendix uploaded by the submitter is checked according to the preset appendix verification rules to obtain the appendix verification result. If the appendix verification result indicates that the appendix uploaded by the submitter has passed the verification, the appendix uploaded by the submitter is determined as the input parameter. The preset appendix verification rules include at least one of the following: appendix format compliance verification, appendix size compliance verification, table header compliance verification, data type and format verification, numerical range verification, appendix type matching verification, appendix and text parameter consistency verification, and professional applicability verification.

7. A method for generating mutual extraction conditions, characterized in that, Applied to a receiving device, the method includes: Receive the mutual submission condition notification sent by the business system associated with the submitting party; According to the preset condition verification rules, the target mutual exchange conditions included in the mutual exchange condition notification are verified to obtain the condition verification results; wherein, the preset condition verification rules include at least one of the following: condition content completeness verification, condition data rationality verification, and design requirement compliance verification. If the verification result indicates that the target mutual transfer conditions have passed the verification, the target mutual transfer conditions will be archived in the receiving condition directory corresponding to the receiving party's major.

8. The method according to claim 7, characterized in that, The method further includes: If the condition verification result indicates that the target mutual extraction condition has not passed the verification, a problem list is generated and sent to the business system associated with the proposing party. Receive a condition change notification sent by the business system associated with the person who made the request, and review the changes to the target mutual request conditions marked in the condition change notification based on the issue list, and obtain the condition review result; If the verification result indicates that the changes to the target mutual transfer conditions have passed the verification, the changed target mutual transfer conditions will be archived in the receiving condition directory corresponding to the receiving party's major.

9. A system for generating mutual extraction conditions, characterized in that, The mutual extraction condition generation system includes a proposing device and at least one receiving device, wherein the proposing device is used to perform the method as described in any one of claims 1 to 6, and the receiving device is used to perform the method as described in any one of claims 7 to 8.

10. A computer device, characterized in that, The computer device is a proposing device and at least one receiving device. The computer device includes a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor. When the processor executes the computer program, the computer device performs the method as described in any one of claims 1 to 6, or performs the method as described in any one of claims 7 to 8.

Images