A project collaboration method

Abstract

This application relates to a project collaboration method, comprising: obtaining the project plan document and initializing the task document corresponding to the ongoing phase; after the target project enters the vendor delivery phase, responding to the vendor's task conclusion editing request, editing and submitting the vendor's task conclusion in the task document; calculating the document pass rate based on the vendor's task conclusion in the task document; if the document pass rate is greater than a preset threshold, setting the target project's progress to the client acceptance phase and notifying the client; after the target project enters the client acceptance phase, responding to the client's acceptance request, editing and submitting the client's acceptance conclusion in the task document; calculating the acceptance pass rate based on the client's acceptance conclusion in the task document; if the acceptance pass rate is greater than a second preset threshold, determining that the target project has passed acceptance. It is evident that this application, by calculating the document pass rate based on the vendor's task conclusion in the task document and using this document pass rate as the acceptance standard for vendor delivery, can improve delivery efficiency.

Description

Technical Field

[0001] This application relates to the field of project collaboration management technology, and in particular to a project collaboration method. Background Technology

[0002] With the increasing demand for cross-regional collaboration, various government-enterprise cooperation, outsourced development, joint research and development and other projects involving collaboration between parties generally rely on online project collaboration platforms to complete the entire process management. The project life cycle mainly includes core stages such as project execution, delivery by the contractor, and acceptance by the client.

[0003] Currently, mainstream project collaboration platforms can only provide basic and simple functions such as task assignment, progress display, and message push. Overall project management largely relies on manual coordination and follow-up. For example, project progress switching and acceptance result judgment all require manual completion. Under this manual management model, the standards for switching project progress nodes are not uniform, and the judgment of acceptance results is highly subjective and inaccurate. This not only significantly reduces the efficiency of project collaboration and acceptance but also easily leads to problems such as misjudgment of project progress and disputes over acceptance results, resulting in poor standardization and reliability of overall project management.

[0004] Therefore, there is an urgent need for an intelligent project collaboration method to solve the above problems. Summary of the Invention

[0005] This application provides a project collaboration method, apparatus, computer equipment, and storage medium, aiming to solve the technical problem of low collaboration efficiency caused by the need for manual coordination and follow-up in traditional project collaboration methods.

[0006] In a first aspect, embodiments of this application provide a project collaboration method, the method being applied to a project collaboration platform, the method comprising: Once the target project enters the in-process phase, obtain the project's planning document; Initialize the target document corresponding to the ongoing stage according to the plan document, wherein the target document includes at least one task document; After the target project enters the delivery phase by Party B, in response to Party B's request to edit the task conclusion, Party B edits and submits the task conclusion of each task document in the at least one task document; Calculate the document pass rate based on the conclusion of the B party's task in each of the at least one task document; If the document pass rate is greater than the first preset threshold, the progress of the target project will be set to the client acceptance stage and the client will be notified. After the target project enters the client acceptance phase, in response to the client's acceptance request, the client's acceptance conclusion for each of the at least one task document is edited and submitted. Calculate the acceptance pass rate based on the client's acceptance conclusion for each of the at least one task documents; If the acceptance pass rate is greater than the second preset threshold, the target project is deemed to have passed acceptance.

[0007] Optionally, initializing the target document corresponding to the ongoing stage based on the plan document includes: Based on the overall work schedule data in the plan document, generate the at least one task document.

[0008] Optionally, the target document further includes a configuration and calculation data document and a notification document. The initialization of the target document corresponding to the ongoing phase based on the plan document includes: Extract job information from the aforementioned planning document; The job information will be synchronized to the corresponding job information in the configuration and calculation data document and the notification document.

[0009] Optionally, the method further includes: Before the target project enters the delivery stage by Party B, a preset timed task is initiated. The preset timed task includes an overdue delivery timed task and a work period reminder timed task. The overdue delivery timed task is used to calculate the overdue rate of the target project and the overdue deduction. The work period reminder timed task is used to trigger a real-time update notification on the project collaboration platform at the start and end times of each progress stage of the target project.

[0010] Optionally, the method further includes: If the planning document is changed, the progress of the target project is set to the in-progress stage, and a new target document is generated based on the changed planning document.

[0011] Optionally, the second party includes the person in charge of the second party and the members of the second party's team. The step of responding to the second party's task conclusion editing request, editing and submitting the second party's task conclusion for each task document in the at least one task document, includes: In response to the task conclusion editing request from the member of Party B, the task conclusion of Party B is edited in the at least one task document and submitted to the person in charge of Party B; In response to the review request from the person in charge of Party B, the task conclusion of Party B shall be reviewed; If the task conclusion of Party B is approved, then the task conclusion of Party B shall be submitted.

[0012] Optionally, the at least one task document includes a target task document, and the method further includes: If the client's acceptance conclusion for the target task document is "not approved", a preset communication record table will be displayed on the project collaboration platform. The preset communication record table is used to facilitate communication between the client and the contractor.

[0013] Optionally, the overdue rate of the target project is calculated using the following formula: , ,

[0014] in, This refers to the actual number of days worked by Party B. The total number of days planned for the project. The actual working time of Party B. This refers to the total working time of Party B. This is an extension of the employee's working hours. The time during which Party A inspects and provides materials during Party B's working hours.

[0015] Optionally, the method further includes: If the overdue rate of the target project is greater than or equal to the first preset threshold, and the overdue rate of the target project is less than the second preset threshold, then a deduction operation will be performed on the target project. If the overdue rate of the target project is greater than or equal to the second preset threshold, and the overdue rate of the target project is less than the third preset threshold, then the project termination option on the project collaboration platform is activated. If the overdue rate of the target project is greater than or equal to the third preset threshold, then the full amount of the target project will be deducted and the target project will be terminated.

[0016] Optionally, each task document's conclusion for Party B corresponds to a Party B conclusion control, and the formula for calculating the document pass rate is:

[0017] in, The number of controls that are deemed qualified by Party B in the conclusion. This represents the total number of conclusion controls for Party B.

[0018] This application provides a project collaboration method. The method is applied to a project collaboration platform and includes: after a target project enters the in-process stage, obtaining a plan document for the target project; initializing a target document corresponding to the in-process stage based on the plan document, the target document including at least one task document; after the target project enters the delivery stage, responding to a task conclusion editing request from the contractor, editing and submitting the contractor's task conclusion for each of the at least one task document; calculating a document pass rate based on the contractor's task conclusions for each of the at least one task document; if the document pass rate is greater than a first preset threshold, setting the target project's progress to the client acceptance stage and notifying the client; after the target project enters the client acceptance stage, responding to the client's acceptance request, editing and submitting the client's acceptance conclusion for each of the at least one task document; calculating an acceptance pass rate based on the client's acceptance conclusions for each of the at least one task document; if the acceptance pass rate is greater than a second preset threshold, determining that the target project has passed acceptance. Therefore, the technical solution of this application calculates the document pass rate based on the contractor's task conclusions for each task document and uses this pass rate as the acceptance standard for the contractor's delivery. On the one hand, this effectively filters out unqualified deliverables and avoids invalid acceptance processes; on the other hand, it forces the contractor to improve delivery quality, significantly reduce rework costs, and improve delivery efficiency. Secondly, this application abandons the traditional subjective acceptance model and automatically calculates the acceptance pass rate based on the client's acceptance conclusions, effectively reducing disputes between the client and contractor caused by ambiguous acceptance standards, thereby reducing manual communication costs and improving the collaboration efficiency between the client and contractor. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0022] Figure 1a A flowchart illustrating a project collaboration method provided in an embodiment of this application; Figure 1b A flowchart illustrating a project collaboration method provided in an embodiment of this application; Figure 1c This is a schematic diagram of the delivery process for the supplier stage provided in the embodiments of this application; Figure 1d This is a schematic diagram of the delivery process for the client stage provided in the embodiments of this application. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of this application. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0025] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0026] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0027] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0028] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0029] To address the technical problem of low collaboration efficiency caused by the need for manual coordination and follow-up in traditional project collaboration methods, this application provides a project collaboration device that can improve project collaboration efficiency.

[0030] Figure 1a This is a flowchart illustrating a project collaboration method provided in an embodiment of this application. In one embodiment, the method is applied to a project collaboration platform, and the method includes steps S101-S107.

[0031] S101. After the target project enters the in-process stage, obtain the project plan document.

[0032] Specifically, the project collaboration page includes: Area A (user name area), Area B (project information area), Area C (project progress bar area), Area D (workgroup members area), Area E (project data area), and Area F (project document area).

[0033] Section A (User Name Section) includes: Page Logo, User Name / Organization, and Messages.

[0034] Section B (Project Information Area) includes: Page Path, Project Name, Project Type, Project Status Area, and Project Multi-Function Button Area. The Project Status Area includes: In Progress, Under Change, Terminating, Completed, and Terminated. The Client's Project Multi-Function Button Area includes: Change & Termination, Cancel Change, Resume Cooperation, and Optimize / Renovate. The Supplier's Representative's Project Multi-Function Button Area includes: More, Cancel Change, and Agree or Disagree to Termination.

[0035] Area D (Workgroup Personnel Area) includes: avatars, tasks, information bars, personnel work status area, and personnel work multi-function button area. Specifically, the Client's work status area includes: overdue payment, overdue acceptance. The Client's multi-function button area includes: acceptance passed or failed, third-party testing, and viewing project completion or termination notification. The Supplier's responsible person's work status area includes: stage overdue days, delivery overdue rate %, and overdue deduction of [amount] yuan. The Supplier's responsible person's multi-function button area includes: deliver to Client, and viewing project completion or termination notification. Team Member 1's work status area includes: overdue deduction of [amount] yuan. Team Member 1's multi-function button area includes: submit to Supplier's responsible person, and viewing project completion or termination notification. Team Member n's work status area includes: overdue deduction of [amount] yuan. Team Member n's multi-function button area includes: submit to Supplier's responsible person, and viewing project completion or termination notification.

[0036] Area E (Project Data Area) includes: project documents and tasks, project folders, and project process records.

[0037] Area F (Project Document Area) includes: Document Operation Button Area: Go to Compile, Go to Modify, Go to Accept, Go to Review and Modify, and Synchronize Modification.

[0038] The document collaboration and communication prompt area includes: Document collaboration in progress, Document communication in progress.

[0039] Specifically, the components of a document editing page are: Section A (User Name Section) includes: Page Logo, User Name / Organization, and Messages.

[0040] Section B (Project Information Area) includes: Project Name, Project Type, Project Status, and Multifunctional Buttons.

[0041] Area C (Document Editing Function Area) includes: document editing, document collaboration, and instant document communication.

[0042] Section D (document tab area) includes: document name, document switching.

[0043] Area E (Document Content Area) includes: viewing and editing document content.

[0044] S102. Initialize the target document corresponding to the ongoing stage based on the plan document.

[0045] The target document includes at least one task document.

[0046] In one embodiment, S102 specifically includes the following steps: S1021.

[0047] S1021. Generate at least one task document based on the overall work schedule data in the planning document.

[0048] In another embodiment, the target document further includes a configuration and calculation data document and a notification document, and S102 specifically includes the following steps: S1022-S1023.

[0049] S1022. Extract job information from the planning document.

[0050] S1023. Synchronize the job information to the corresponding job information in the configuration and calculation data document and the notification document respectively.

[0051] It should be noted that, specifically, after Party A completes the project fee payment, the startCooperation method is called to verify whether the number of days filled in the requirements document is greater than the remaining number of days in the current dispute period of the project.

[0052] When synchronizing the "Configuration and Calculation Data Document" and the "Notification Document," the system first retrieves the index set of newly added job rows from the "Plan Document" based on the `curAdd` attribute, and the index set of hidden job rows based on the `show` attribute. Then, based on the obtained index sets, the synchronization operation for the newly added and hidden job rows is completed. After synchronization, the table structure of the "Plan Document," "Configuration and Calculation Data Document," and "Notification Document" will be consistent, and subsequent project settlement will be processed based on this unified table structure.

[0053] Configure the project start time in the "Plan Document" to the current time. The document will generate the planned completion time for each stage based on the start time, the number of working days filled in, the number of acceptance days, and other data. Then, based on the planned completion time, it will complete the progress bar node processing and project time data calculation.

[0054] Based on the overall work schedule data in the "Plan Document", the planned completion time of the project is stored for processing the planned completion time data of the progress bar cooperation nodes.

[0055] Complete the progress bar node processing, store the time of the negotiation completion node, and insert the corresponding stage node, node description and planned time based on the overall work schedule data in the "Plan Document".

[0056] Store the project start time in the pp_project database table, change the phase field (project phase) to ON_GOING, and change the projectStatus field (project status) to PROGRESS to indicate that the project is in the "in progress" phase; set the onGoingPhase field (phase number) to identify the specific phase number of the project.

[0057] The project member set is retrieved by querying the pp_project_member database table; the overdue values ​​of the project members are initialized and stored in the pp_phase_cooperate_overdue_value database table for displaying overdue data in the avatar area; the collaboration status of the project members is initialized and stored in the pp_phase_cooperate_status database table for determining the collaboration status of Party A and Party B, Party B's representative, and team members; the takeover status of the team members is initialized and stored in the pp_member_take_over_status database table for determining the takeover status of the team members by Party B's representative.

[0058] After initializing the phase submission count object, set the checkNum attribute (number of reviews) to 0 and the deliverNum attribute (number of deliveries) to 0. After initialization, store the object in the pp_phase_hand_over_num database table. This object is used to support the operation of business logic such as delivery count judgment, acceptance count judgment, team member submission count judgment, termination type count statistics, and display of client evaluation / acceptance reminders.

[0059] Modify the value of the projectPhase attribute in the pp_phase_cooperate_message database table to ON_GOING, thereby updating the message identifier in the avatar area from the "negotiation" stage to the "in progress" stage.

[0060] Copy the documents and related references from the "negotiation" stage to the project in the "in progress" stage to isolate them from the documents in the negotiation stage. The "in progress" stage only performs editing operations on the documents of this stage. Configure the corresponding docId for each document in the project document list with the document name "Plan Document" to enable the function of opening the corresponding document by clicking the document name.

[0061] The work time periods in the "Plan Document" are stored in the work_time_period database table. At the same time, the work time period content in the document is locked to prevent modification. This data is used for project time calculation.

[0062] In the "Plan Document", the current value of the cost cell is stored in the extended field ext for configuring cost change prompts in the document; after the project enters the in-progress stage, the configuration text line that prompts the project cost changes is hidden.

[0063] The project folder is synchronized based on the project document list within the "Project Documentation" document, allowing for viewing of the project folder on the project collaboration page. This section contains common method logic and is only explained in detail here; it will not be repeated later. The `syncProjectDirectory` public method is called to extract the project document list from the "Project Documentation" document, returning a `List`. <file>A collection of documents in a formatted list, where File objects contain attributes such as name, type (folder / document), document ID, and parent folder ID; then based on a List... <file>Build a List <phasedoclibpo>The formatted collection of phase documents, after setting the document version number by the phase number and the number of changes, is stored in the pp_phase_doc_lib database table.

[0064] The number of prototype rows in the synchronized test report document is part of the common method logic and will only be explained in detail here, without being repeated later. The `syncTestReportPrototypeNumber` common method is called to extract the number of prototypes corresponding to the test report in the "Plan Document," and based on this, the number of prototype rows in the test report document can be added, deleted, or retained.

[0065] Extract the personnel information from the "Plan Document" and update the personnel data in the pp_project_member database table (project member table) synchronously, so that the personnel's corresponding position data can be displayed in the project center list.

[0066] Based on the current document data, update the existPackageSample and nowPhaseExistBudget attributes and store them in the pp_phase_hand_over_num database table. The existPackageSample indicates whether a packaging / poster sample has been made, with a value of 0 representing no and a value of 1 representing yes. It is used to determine whether the non-conforming delivery termination process can be initiated when the client fails to accept the product. The nowPhaseExistBudget indicates whether there is a budget in the current stage, with a value of 0 representing no and a value of 1 representing yes. It is used to determine whether the budget content block is displayed or hidden.

[0067] Based on the overall work schedule data in the "Plan Document", the task document for the current stage is generated and stored in the pp_doc_task database table. This is used to display the task document button and status on the front end. At the same time, the isDeliver field (deliverable field) of the corresponding document in the pp_phase_doclib database table is updated to 1 to indicate that the document needs to be delivered in the current stage.

[0068] Retrieve all test report documents and complete the configuration of the name and version cell content for the corresponding test report documents.

[0069] Once the negotiations are completed, the delivery phase begins, at which point document permission allocation needs to be completed.

[0070] (1) Party A has viewing permissions for its own task documents and sets the docView attribute to true; if the project is a graduation project, Party A also has viewing permissions for other documents and sets the docView attribute to true; if the project is not a graduation project, Party A does not have viewing permissions for other documents and sets the docView attribute to false.

[0071] (2) For the documents to be delivered by the person in charge of Party B and the documents to be delivered by the personnel under management, set the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties to true; for the invoice documents that do not need to be delivered by the person in charge of Party B and the invoice documents that do not need to be delivered by the personnel under management, set the docView property to true; for the non-invoice documents that do not need to be delivered by the person in charge of Party B and the non-invoice documents that do not need to be delivered by the personnel under management, set the docView, docEdit, and leaderConclusionHeader properties to true.

[0072] (3) If a team member is taken over, the team member can only view all documents, and the docView property is set to true; if a team member is not taken over, the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties are set to true for the documents to be delivered to the team member; the docView property is set to true for the invoice documents to be delivered to the team member; and the docView, docEdit, and leaderConclusionHeader properties are set to true for the non-invoice documents to be delivered to the team member.

[0073] Based on the current requirements document and the "Plan document" data, calculate the job combination type and store it in the pp_project database table. This is used to calculate the delivery document achievement rate. Then, combined with the achievement rate, document qualification rate, and acceptance rate, the task document status is determined.

[0074] Store the process operation record after the negotiation is completed, and update the avatar area and to-do items.

[0075] If the project is a graduation project, the contractor's conclusions and the client's acceptance conclusions in the project proposal should be reset during the proposal stage.

[0076] For all logistics documents, set the editable attribute based on whether there is a logistics days, thereby controlling the editability of the third-party logistics radio button.

[0077] Export the materials from the requirements document, determine the usage status of the materials in the project, and update the material data in the project library synchronously.

[0078] Start the "Overdue Delivery" scheduled task to calculate the project's overdue rate and overdue deduction amount.

[0079] Start the "Work Hour Reminder" scheduled task to trigger real-time page update notifications at the start and end times of the project's work hours.

[0080] Synchronize the information in the "Configuration and Calculation Data Document" such as the total number of working days and the number of project phases of Party B. This information is used for the calculation of fees and credit scores in the notification letter.

[0081] Copy the requirements document, the plan document, and other documents, and set the phaseDocType attribute to CHANGE_RECORD (change record). After the requirements are changed during subsequent project collaboration, project members can click the "Change Record" option in the project folder to view the data of the requirements document and the plan document at the time of the negotiation.

[0082] Ultimately, the front-end is notified via web-socket to update the project collaboration page and document page in real time, and to trigger the playback of to-do notification sounds; at the same time, the WeChat API interface is called to send WeChat notifications to the corresponding users.

[0083] S103. After the target project enters the delivery phase by Party B, in response to Party B's request to edit the task conclusions, Party B shall edit and submit the task conclusions of Party B for each task document in at least one task document.

[0084] S104. Calculate the document qualification rate based on the conclusion of Party B's task in each of at least one task document.

[0085] S105. If the document pass rate is greater than the first preset threshold, the progress of the target project will be set to the client acceptance stage and the client will be notified.

[0086] It should be noted that S103-S105 will be explained in detail below.

[0087] Please see Figure 1c This is a flowchart illustrating the execution of the vendor's delivery phase, as provided in this application embodiment. Specifically, during the vendor's delivery phase, the core task of the vendor's staff is to complete the task document preparation for the corresponding phase. This phase can utilize document collaboration features to invite other project members to participate in collaborative document editing. If the project has vendor team members, each team member must first submit their completed document to the vendor's manager for review and modification. After all team members have submitted and the vendor's manager has reviewed and modified the document, the vendor's manager will then deliver it to the client. If, after some team members have submitted, other project members edit the document to be delivered, the system will trigger a synchronized modification logic. The team members who have already submitted must check whether the edited content affects the document module they are responsible for, make adjustments, and resubmit to the vendor's manager. During the vendor's delivery phase, the vendor's manager can take over the documents managed by team members, complete the editing, and deliver them uniformly. If the project does not have vendor team members, the vendor's manager will directly deliver the document to the client after completing the document editing and meeting the requirements. During this phase, the client can initiate a requirement change operation to modify documents such as the "Requirements" and "Plan" and to redefine project requirements and plans.

[0088] This application embodiment configures a total of 22 controls and 43 document editing function types. Each type of control and function corresponds to independent interaction logic and operation specifications, and is designed around the goals of improving user document creation efficiency, standardizing document management, and ensuring document consistency.

[0089] The staff of Party B shall, in accordance with the established requirements, verify and fill in the relevant content of the task documents.

[0090] Whether a task document is complete is determined based on the conclusions of Party B within the document. These conclusions can be implemented using a drop-down list control or by configuring cells in the program. The drop-down list control for Party B's conclusions uses a yellow background to prompt the user to complete the editing operation. A task document may contain multiple drop-down list controls for Party B's conclusions. If a document contains multiple drop-down list controls for Party B's conclusions, the completion rate must be considered in conjunction with the pass rate to determine whether the document meets the current stage's document achievement rate requirements, and the corresponding document status should be set accordingly. If the conclusions for Party B's conclusions are configured by the program, the completion of the document is determined based on the content entered in the document, and the conclusions for Party B's conclusions are updated synchronously.

[0091] In one embodiment, each task document's conclusion corresponds to a corresponding conclusion control, and the formula for calculating the document pass rate is:

[0092] in, The number of controls that are deemed qualified by Party B in the conclusion. This represents the total number of conclusion controls for Party B.

[0093] The following describes the document collaboration process among the various members of Party B during the delivery phase.

[0094] During the delivery phase by Party B, when Party B members are editing task documents, the "Document Collaboration" button on the task document will remain active. Party B can enable the "Document Collaboration" function to invite other project members to participate, and switch the document editing permissions through operations such as requesting editing, exiting editing, and countdown to collaboratively complete the task document compilation.

[0095] The contractor's representative can take over the task documents assigned by team members, complete the editing and submission operations. The operation path is: click the "More" button, then select the "Take Over Team Member's Document Task" button. The system will display a list of team members. Check the corresponding team member's checkbox and click "OK" to complete the takeover. This function is used to deal with unexpected situations encountered by the contractor's team members during project execution. For example, if a team member is unable to complete the document preparation and submission on time due to personal reasons, the contractor's representative can directly take over the team member's document task to avoid affecting the overall project progress.

[0096] The takeover operation must meet the following conditions: the project is currently in the contractor's delivery phase and is not in the review / revision phase, project initiation / termination phase, client acceptance phase, or project suspension phase.

[0097] The system will update the corresponding takeover status (1 for taken over, 2 for not taken over) to the pp_member_take_over_status database table based on the selected member's user ID.

[0098] First, query the historical list of team members already taken over and the list of team members to be taken over by the person in charge of Party B this time. If there are no changes in the two lists, the interface will return directly without performing any subsequent operations.

[0099] Subsequently, the person in charge of Party B revoked the operation permissions of the original team members' task documents, and set docEdit (document editability permission), leaderConclusion (Party B's conclusion editability permission), leaderConclusionHeader (Party B's conclusion button clickability permission), and communicateRecordTableLeaderCol (Communication record table Party B column permission) to false.

[0100] After completing the above steps, restore the original group member's access permissions to their own task documents, according to the following rules: (1) For documents that need to be delivered and whose acceptance conclusion by Party A is not passed, set the viewing permission, editing permission, Party B's conclusion permission, and Party B's column permission in the communication record form to true.

[0101] (2) For documents that need to be delivered and whose acceptance conclusion by Party A is not "not passed", set the viewing permission, editing permission, Party B's conclusion permission, and Party B's conclusion button permission to true.

[0102] (3) For documents that do not require delivery and are not invoices, set the viewing and editing permissions to true.

[0103] If there are any team members to be taken over, update the access permissions of the contractor's representative for the aforementioned team members' documents, according to the following rules: (1) For documents that need to be delivered and whose acceptance conclusion by Party A is not passed, set the viewing permission, editing permission, Party B's conclusion permission, and Party B's column permission in the communication record form to true.

[0104] (2) For documents that need to be delivered and whose acceptance conclusion by Party A is not "not passed", set the viewing permission, editing permission, Party B's conclusion permission, and Party B's conclusion button permission to true.

[0105] (3) For documents that do not require delivery and are not invoices, set the viewing and editing permissions to true.

[0106] The team member under management retains only viewing permissions for their own documents; editing permissions, permissions for the "Party B's Conclusion" button, and permissions for the "Party B's Conclusion" column in the communication record form are all set to false.

[0107] The system retrieves all task documents with document collaboration enabled and removes the assigned team member from the collaboration invitation list for the corresponding document.

[0108] If there are any team members who have not been taken over, and all of them have submitted their work to the vendor's representative, the collaboration status between the vendor and all team members will be set to DOCUMENT_CHECK (document review and revision). The project will then enter the review and revision phase, requiring a reassignment of document operation permissions. This permission allocation logic is a public method, which will only be explained in detail here and will not be repeated later. This time, the public method documentCheckAllMemberDistribute is called, and the permission allocation rules are as follows: (1) Party A's permissions to all group members' documents: If the project is a graduation project, set the viewing permission to true; otherwise, set it to false.

[0109] (2) Permissions of Party B's representative to all team member documents: For documents that the managed team member needs to deliver and Party A's acceptance conclusion is "not approved", set the permissions to view, edit, Party B's conclusion, and Party B's column in the communication record form to true; For documents that the managed team member needs to deliver and Party A's acceptance conclusion is not "not approved", set the permissions to view, edit, Party B's conclusion, and Party B's conclusion button to true; For invoice documents that the managed team member does not need to deliver, set the permission to view to true; For non-invoice documents that the managed team member does not need to deliver, set the permissions to view and edit to true; For documents that non-managed team members need to deliver and Party A's acceptance conclusion is "not approved", set the permissions to view, edit, Party B's conclusion, and Party B's column in the communication record form to true; For documents that non-managed team members need to deliver and Party A's acceptance conclusion is not "not approved", set the permissions to view, edit, Party B's conclusion, and Party B's conclusion button to true; For documents that non-managed team members do not need to deliver, set the permission to view to true.

[0110] (3) Permissions of the managed team members to documents: set the viewing permission to true; set the viewing and editing permissions to true for non-invoice documents that they do not need to deliver, and set the viewing permission to true for other documents.

[0111] If all team members have been taken over, it is necessary to determine whether the conditions for delivery to Party A are met based on the current project document status. This determination logic is a public method, which will only be explained in detail here and will not be repeated later. This time, the public method checkCanDelivery is called, and the determination rules are as follows: If the project is currently in the source file delivery stage, delivery can be made if all of the following conditions are met: the status of all source files of Party B's responsible person is CAN_SUBMIT_DELIVERY (can be submitted for delivery), the pass rate of all source files of the taken-over team members is 100%, and the status of all source files of the non-take-over team members is CHECK_PASS (approved after review and modification); If the project is currently in the non-source file delivery stage, delivery can be made if all of the following conditions are met: the status of all documents to be delivered by Party B's responsible person is CAN_SUBMIT_DELIVERY (can be submitted for delivery), the status of documents to be delivered by all the taken-over team members is CAN_SUBMIT_DELIVERY (can be submitted for delivery) or SYNC_MODIFY (synchronized modification) or IS_SYNC_MODIFY (being synchronized modification), and the status of all source files of the non-take-over team members is CHECK_PASS (approved after review and modification).

[0112] After the above operations are completed, the system notifies the front end via web-socket to update the project collaboration page and document page in real time.

[0113] In this embodiment, the process for determining whether a team member can submit a document to the person in charge of Party B is as follows: After calling the public method checkCanSubmitToLeader, firstly, all documents are queried. If the document status is not WAIT_COMPILE (to be compiled), it means that the document has been opened and operated by its owner. Then, all team members are traversed. If the leaderConclusion attribute of all task documents belonging to a certain team member is COMPLETE (completed), and the qualifiedRate attribute of inspection reports, checklists, and review reports meets the current stage document achievement rate requirement, then the collaboration status between the person in charge of Party B and the team member is updated to CAN_SUBMIT (can be submitted). Otherwise, it is updated to DOCUMENT_COMPILE (document compilation) or MODIFY_AGAIN_SUBMIT (modify and resubmit).

[0114] After a team member clicks the "Submit to the B2B Representative" button, the system first verifies that the current collaboration status between the team member and the B2B representative is CAN_SUBMIT (submission is possible) and that the current time is within the project's working time period.

[0115] After verification, the collaboration status between the current team member and the person in charge of Party B will be changed to DOCUMENT_CHECK (document review and modification).

[0116] Record this as the number of submissions by this team member and save the information to the pp_phase_hand_over_num database table. The business logic during the saving process will automatically retrieve the submission count information.

[0117] If the group member is not the last member to complete the submission, perform the following operations: update the group member's avatar information, record the process log of the group member's document submission, change the current status of the group member's task document to WAIT_CHECK (pending review), and reassign the operation permissions of each project member for the group member's document, according to the following rules: (1) Party A's permissions to the group member's documents: If the project is a graduation project, set the viewing permission to true; otherwise, set it to false. All other permissions should be set to false.

[0118] (2) The permissions of the person in charge of Party B to the group member’s documents: only the viewing permission is set to true, and all other permissions are set to false.

[0119] (3) Other group members’ permissions to this group member’s document: Viewing permission only.

[0120] (4) The group member’s permissions for his own documents: For non-invoice documents that do not need to be delivered, set the viewing and editing permissions to true; for other documents, set the viewing permission to true only.

[0121] If the team member is the last member to complete the submission, perform the following operations: save the process log of the last team member's document submission, update the avatar area information and to-do items messages, change the current task document status of all team members to WAIT_CHECK (pending review and modification), change the collaboration status of all team members and the contractor's representative to DOCUMENT_CHECK (document review and modification), the project enters the review and modification stage, and call the public method documentCheckAllMemberDistribute to complete the document permission allocation. This logic has been explained in detail above and will not be repeated here.

[0122] After the above operations are completed, the system notifies the front end via web-socket to update the project collaboration page and document page in real time, triggers a to-do notification sound, and calls the WeChat API interface to send a WeChat notification to the corresponding user.

[0123] It should be noted that the logic for synchronous modification by Party B members is detailed below: When some team members have completed document submission, but not all team members have completed submission, if a project member modifies the document to be delivered, the system will trigger the synchronization modification logic.

[0124] Upon triggering the logic, the following operations are performed on team members who have completed submissions: Update the team member's avatar information and to-do list message; change the team member's collaboration status with the vendor's representative to CAN_SUBMIT (can be submitted); change the status of the corresponding submitted document to SYNC_MODIFY (synchronized modification); if the submitted team member has been taken over, update the vendor's representative's permissions for that team member's document; otherwise, update the submitted team member's permissions for their own document, with the following permission rules: (1) For documents that need to be delivered and whose acceptance conclusion by Party A is not passed, set the permissions for viewing, editing, Party B's conclusion, and Party B's column in the communication record form to true.

[0125] (2) For documents that need to be delivered and whose acceptance conclusion by Party A is not "not passed", set the permissions of the "View", "Edit", "Party B's Conclusion", and "Party B's Conclusion" buttons to "true".

[0126] (3) For documents that do not require delivery and are not invoices, set the viewing permission to true.

[0127] After the operation is completed, the system notifies the front end via web-socket to update the project collaboration page and document page in real time, triggers the to-do notification sound, and calls the WeChat API interface to send a WeChat notification to the corresponding user.

[0128] It should be noted that the following describes the execution logic for cases where the review fails.

[0129] The person in charge of Party B clicks the "Review Failed" button. The collaboration status of Party B's person in charge and all team members is verified to be CAN_CHECK_NO_PASS, indicating that the review and modification cannot be approved. This is within the working time period.

[0130] Record the number of times the document was reviewed and revised, and save it to the pp_phase_hand_over_num database table.

[0131] Save the process record of failed reviews and updates the profile picture area and to-do items.

[0132] Change the collaboration status of the B2B representative and all team members to MODIFY_AGAIN_SUBMIT (modify and resubmit), change the collaboration status of the B2B representative and all individual team members to MODIFY_AGAIN_SUBMIT (modify and resubmit), change the task document status of all team members to WAIT_MODIFY (pending modification), and reset the B2B conclusion in the task documents of all team members.

[0133] If the revision fails, assign document permissions: (1) Party A shall set the document access permission for all group members to true if it is a graduation project, otherwise set it to false.

[0134] (2) The B2B representative's document permissions for all team members: For documents that the managed team members need to deliver but which have not passed the A-side acceptance review, the B2B representative's permissions for viewing, editing, B2B conclusion, and the B2B column of the communication record form should be set to true. For documents that the managed team members need to deliver but which have not passed the A-side acceptance review, the B2B representative's permissions for viewing, editing, B2B conclusion, and the B2B conclusion button should be set to true. For invoice documents that the managed team members do not need to deliver, the viewing permission should be set to true. For non-invoice documents that the managed team members do not need to deliver, the viewing and editing permissions should be set to true. For documents belonging to non-managed team members, the viewing permission should be set to true.

[0135] (3) For team members under management, set the viewing permission to true. For team members not under management, set the viewing, editing, supplier conclusion, and communication record sheet supplier column permissions to true for documents they need to deliver that have not been accepted by Party A. For documents they need to deliver that have not been accepted by Party A, set the viewing, editing, supplier conclusion, and supplier conclusion button permissions to true. For non-invoice documents they do not need to deliver, set the viewing and editing permissions to true. For their other documents, set the viewing permission to true. For other people's documents, set the viewing permission to true.

[0136] Finally, the web-socket notification system sends real-time updates to the front-end project collaboration page and document page, sends to-do notification sounds, and calls the WeChat API to send WeChat notifications to the corresponding users.

[0137] The person in charge of Party B clicks the "Deliver to Party A" button. The collaboration status between Party B and Party A is verified to be CAN_DELIVER (deliverable), and the current working time period is within the specified time frame.

[0138] If the delivered document contains logistics documents, set the logistics content block for this delivery as history, making it uneditable.

[0139] Record which delivery this is, determine and record whether there is a process for the client to return items during this stage of acceptance, set the acceptance prompt attribute of assessTipsFlag to 1 (the client opens the project collaboration page and a friendly acceptance prompt pops up), and set the acceptanceAssessFirstTipsFlag attribute of the client's first acceptance prompt to 1 (the client is currently on the project collaboration page and a friendly acceptance prompt pops up), and save it to the pp_phase_hand_over_num database table.

[0140] If there is a process for Party A to return items during this acceptance process, the status of the "Returned Items" document should be changed to WAIT_COMPILE pending compilation in advance, the content blocks of the document should be copied, and the return count should be incremented by 1. During the acceptance process, if the collaboration status between Party A and Party B is "acceptance failed", this document should be displayed.

[0141] If there are team members in the project, the process log saves the document review and approval records.

[0142] Change the collaboration status between the person in charge of Party A and Party B to DOCUMENT_ACCEPTANCE (document acceptance) to determine if the project is in the acceptance period of Party A. Change the status of all delivered documents to WAIT_ACCEPTANCE_CHECK (pending acceptance) to handle the buttons and status text of task documents.

[0143] If the process is in the "A provides items" phase, after B delivers the items to A, it means that B has inspected and approved the items provided by A, and the "A provides items" phase ends. Set the isPartyAProvidePhase property to 0 (1 represents the "A provides items" phase, 0 represents the opposite), set the leaderAcceptancePartyAProvide property to 1 (1 represents B inspecting the items provided by A), and delete the scheduled task corresponding to the "A provides items" phase.

[0144] Determine if logistics information exists in the submitted document and save it to the pp_phase_hand_over_num database table. If it exists, start the scheduled logistics task after delivery by Party B, subscribe to third-party logistics information, and continue until the logistics is signed for or the scheduled logistics timeout reaches the maximum.

[0145] During the project's acceptance phase by the client, document permissions were assigned as follows: (1) For standard acceptance, the client sets the viewing and editing permissions to true for their own task documents, and sets the viewing, client acceptance, and client acceptance button permissions to true for documents to be delivered at the current stage. For other documents, if it is a graduation project, the viewing permission is set to true; otherwise, no permissions are granted. For partial acceptance, the client sets the viewing and editing permissions to true for their own task documents, and sets the viewing, client acceptance, and client acceptance button permissions to true for all non-source files. For other documents, if it is a graduation project, the viewing permission is set to true; otherwise, no permissions are granted. For source file acceptance, the client sets the viewing, client acceptance, and client acceptance button permissions to true for all source file documents, and sets the viewing and client acceptance button permissions to true for other documents.

[0146] (2) For standard acceptance, the contractor's representative should set view and edit permissions to true for non-invoice documents that they do not need to deliver, and set view permissions to true for other documents. For non-invoice documents that the managed personnel do not need to deliver, the contractor should set view and edit permissions to true, and set view permissions to true for other documents of the managed personnel. For partial acceptance, the contractor's representative should set view permissions to true for all documents. For source file acceptance, the contractor's representative should set view permissions to true for all documents.

[0147] (3) For standard acceptance, the team member under management sets the viewing permission to true, and the team member not under management sets the viewing and editing permissions to true for non-invoice documents that they do not need to deliver, and sets the viewing permission to true for other documents. For partial acceptance, team members set the viewing permission to true for all documents. For source file acceptance, team members set the viewing permission to true for all documents.

[0148] Call the `projectOverdueRate` public method to calculate the current project's overdue rate.

[0149] In one embodiment, the overdue rate of the target project is calculated using the following formula: , ,

[0150] in, This refers to the actual number of days worked by Party B. The total number of days planned for the project. The actual working time of Party B. This refers to the total working time of Party B. This is an extension of the employee's working hours. The time during which Party A inspects and provides materials during Party B's working hours.

[0151] Call the public method modifyPhaseNodePostponementTime to update the estimated completion time of the progress bar, as explained in detail above.

[0152] Finally, the web-socket notification system sends real-time updates to the front-end project collaboration page and document page, sends to-do notification sounds, and calls the WeChat API to send WeChat notifications to the corresponding users.

[0153] It should be noted that during the delivery period, if either Party A or Party B needs to change the requirements, they can negotiate and communicate before Party A initiates the requirement change function, entering the "Change" phase to modify the project requirements and plans. The prerequisites for Party A to initiate a requirement change are: (1) During non-source document delivery period.

[0154] (2) During the period not during the acceptance by Party A.

[0155] (3) Non-project proposal stage.

[0156] (4) If the goods were provided to Party A during the period of providing the goods, and the goods provided by Party A were not in transit or the goods had been delivered.

[0157] (5) The number of times the change is initiated is less than the number of times the configuration is configured.

[0158] (6) The number of valid changes in the current stage is less than the number of configurations.

[0159] (7) During working hours.

[0160] S106. After the target project enters the client's acceptance phase, in response to the client's acceptance request, edit and submit the client's acceptance conclusion for each task document in at least one task document.

[0161] S107. Calculate the acceptance pass rate based on the client's acceptance conclusion for each task document in at least one task document. S108. If the acceptance pass rate is greater than the second preset threshold, the target project is deemed to have passed acceptance.

[0162] It should be noted that S106-S108 will be explained in detail below.

[0163] Please see Figure 1d , Figure 1d This is a schematic diagram of the client's phased delivery process provided in this application embodiment. For the client to activate the "Acceptance Failed" button, the following conditions must be met simultaneously: the client has completed the acceptance process for all documents delivered by the vendor; all documents have generated client acceptance conclusions; the communication record form has been completed; some documents have a status of ACCEPTANCE_CHECK_NO_PASS (i.e., acceptance failed); the current time is within a working period; and the current number of acceptances is less than the maximum number of acceptances configured in the backend.

[0164] It is necessary to verify whether the current time is within the working period, query the pp_phase_cooperate_status data table, obtain the cooperativeStatus attribute value (i.e., cooperation status), and verify whether the current cooperation status is equal to CAN_ACCEPTANCE_NO_PASS (i.e., it fails the evaluation).

[0165] After the acceptance process fails, the "Communication Record Form" should be configured as follows: If the cells in the "Party A" column already contain content, the editable attribute of those cells should be set to false (i.e., uneditable), and the relevant content should be treated as historical data and no longer allowed to be modified.

[0166] Increment the number of times the client has accepted the data by 1, and set the `assessTipsFlag` and `acceptanceAssessFirstTipsFlag` attributes to 0. If this is the `acceptanceMax`th acceptance (i.e. the maximum number of acceptances configured), the client can only perform the operation of "acceptance passed".

[0167] If there are returned item documents from Party A during this acceptance process, the status of the corresponding document must be updated to WAIT_ASSESS (this enumeration value is used to configure the display text for the returned status); in the "Returned Items" document, the content block corresponding to the returned item must be marked as history and set to an uneditable state.

[0168] Change the collaboration status between Party A and Party B's responsible person to MODIFY_AGAIN_DELIVER (i.e., modify and deliver), change the collaboration status between Party B's responsible person and all team members, and individual team members to MODIFY_AGAIN_SUBMIT (i.e., modify and submit), and change the status of all task documents to WAIT_MODIFY (i.e., pending modification).

[0169] Reset the conclusions of Party B in all task documents.

[0170] If the content delivered by Party B at the current stage includes logistics documents, a copy operation must be performed on the logistics content blocks in the logistics documents, and the delivery count marked in the content block title must be incremented by 1.

[0171] Once the process enters the vendor delivery phase, document permission allocation is performed according to the following rules: (1) For standard or partial acceptance: Party A has viewing permissions for its own task documents and must set the docView attribute to true; if the project is a graduation project, Party A has viewing permissions for other documents and sets the docView attribute to true, otherwise, viewing permissions are not granted and the docView attribute is set to false. For source file acceptance: Party A sets the docView attribute to true for non-source file documents; if the project is a graduation project, Party A has viewing permissions for other documents and sets the docView attribute to true, otherwise, viewing permissions are not granted and the docView attribute is set to false.

[0172] (2) For general or partial acceptance: For documents to be delivered by the person in charge of Party B and documents to be delivered by the personnel under management, set the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties to true; For invoice documents that do not need to be delivered by the person in charge of Party B and invoice documents that do not need to be delivered by the personnel under management, set only the docView property to true; For non-invoice documents that do not need to be delivered by the person in charge of Party B and non-invoice documents that do not need to be delivered by the personnel under management, set the docView, docEdit, and leaderConclusionHeader properties to true. For source file acceptance: For source files of the person in charge of Party B and the personnel under management whose acceptance conclusion from Party A is "not passed", set the docView, docEdit, leaderConclusion, and communicateRecordTableLeaderCol properties to true; For source files of the person in charge of Party B and the personnel under management whose acceptance conclusion from Party A is not "not passed", set the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties to true; For other documents, set only the docView property to true.

[0173] (3) For regular or partial acceptance: If a team member has been taken over, the team member only has viewing permissions for all documents, and the docView property is set to true; if a team member has not been taken over, for the documents to be delivered by the team member, the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties are all set to true; for the invoice documents to be delivered by the team member, only the docView property is set to true; for the non-invoice documents to be delivered by the team member, the docView, docEdit, and leaderConclusionHeader properties are set to true. For source file acceptance: If a team member has been taken over, that team member only has view permissions for all documents, and the docView property is set to true; if a team member has not been taken over, for source files belonging to that team member that have been rejected by the client, the docView, docEdit, leaderConclusion, and communicateRecordTableLeaderCol properties are all set to true; for source files belonging to that team member that have been accepted by the client but not rejected, the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties are all set to true; for all other documents, only the docView property is set to true.

[0174] After the client's acceptance process is completed, delete the "Overdue Acceptance" scheduled task.

[0175] Record the end time of this acceptance event and save it to the pp_event_record data table for use in project-related time calculations.

[0176] Save the process record of the operation when the client fails the acceptance test, and update the profile picture area and pending items.

[0177] Call the `projectOverdueRate` public method to calculate the current project's overdue rate. The relevant rules have been explained in detail above.

[0178] Call the public method modifyPhaseNodePostponementTime to update the estimated completion time of the progress bar. The relevant rules have been explained in detail above.

[0179] Start the scheduled task "Party B fails to deliver on time" for calculating the project overdue rate and processing deductions.

[0180] Finally, the front-end is notified via web-socket to update the project collaboration page and document page in real time, and to trigger a to-do notification sound; at the same time, the WeChat API is called to send WeChat notifications to the corresponding users.

[0181] In one embodiment, if the target project needs to be re-delivered, the client needs to click the re-delivery button on the project collaboration platform.

[0182] In one embodiment, when Party A accepts the documents delivered by Party B, if the selected acceptance conclusion is "acceptance failed," the "Communication Record Form" remains permanently displayed, and the document status is set to ACCEPTANCE_CHECK_NO_PASS (i.e., acceptance failed) or ACCEPTANCE_CHECK_NO_PASS_NO_COMPLETE_RECORD_TABLE (i.e., acceptance failed, communication record form incomplete). At this time, the "Instant Communication" button is activated. Party A can enable the instant communication function and fill in the "Communication Record Form" through operations such as requesting editing, exiting editing, and countdown, to communicate with Party B members to resolve issues. The filled content will be archived as historical records.

[0183] In one embodiment, the process for achieving full acceptance is described as follows: For Party A to activate the "Acceptance Passed" button, the following conditions must be met simultaneously: Party A has completed the acceptance of all documents delivered by Party B, Party A's acceptance conclusion for all documents is "Passed", and the current time is within the working hours.

[0184] Query the pp_phase_cooperate_status data table to obtain the cooperateStatus (i.e., cooperation status) attribute value, and verify whether the current cooperation status is equal to CAN_ACCEPTANCE_PASS (i.e., acceptance has passed).

[0185] If the default acceptance is triggered due to failure to accept the goods within the specified period, the text "Default acceptance passed, no field filled in" must be entered in the blank column for Party B in the "Communication Record Form".

[0186] After the acceptance process is completed, the "Communication Record Form" should be set as follows: If the cells in the same row of Party A's column or Party B's column already contain content, the editable attribute of all cells in that row should be set to false (i.e., uneditable). The content of that row will then be treated as historical data and will no longer be allowed to be modified.

[0187] After acceptance testing is completed, before proceeding to the next stage, document permission allocation for the current stage must be finalized, and then the front-end must be notified to update the document page. The permission allocation rules are as follows: (1) For documents that have been delivered and do not need to be delivered again, documents that need to be delivered in the current stage, and documents such as "Requirements", "Plan", "Solution" and "Items Provided by Party A", Party A's docView viewing permission is set to true; if the project is a graduation project, Party A has viewing permission for the other documents and the docView attribute is set to true, otherwise, viewing permission is not granted and the docView attribute is set to false.

[0188] (2) The person in charge of Party B and the team members shall set the docView property of all documents in the current stage to true.

[0189] If the default acceptance is passed, and the collaboration status of both parties is CAN_ACCEPTANCE_NO_PASS (meaning the acceptance failed), and there are items returned by Party A at the current stage, the corresponding content block in the "Returned Items" document should be marked as history and set to an uneditable state.

[0190] Increment the number of times the client accepts data by 1, set the assessTipsFlag and acceptanceAssessFirstTipsFlag attributes to 0, and reset the number of deliveries, acceptances, and other related attributes.

[0191] If this acceptance is an overdue acceptance, the overdue acceptance value of Party A needs to be cleared and updated and saved in the pp_phase_cooperate_overdue_value data table.

[0192] If the client has not selected a scheme in the "Design Scheme" document, the first scheme will be selected by default.

[0193] Once the acceptance is successful, the user-entered content in the invoice document in the current task document will be marked as history and set to an unmodifiable state.

[0194] Save the operation process record of the client's successful acceptance, and update the profile picture area and pending items.

[0195] Change the collaboration status between Party A and Party B's representative to DOCUMENT_COMPILE (i.e., document creation), and change the collaboration status between Party B's representative and all team members, as well as between Party B's representative and individual team members, to DOCUMENT_COMPILE (i.e., document creation). This setting is used to determine the collaboration status between Party A and Party B, and between Party B's representative and team members.

[0196] Increment the onGoingPhase number of the project by 1, reset the overdue value, main reasons for changes / maintenance upgrades, content and other related data of the previous stage, and avoid the above data from affecting the business logic of the next stage.

[0197] Copy the documents and related references from the current stage to the next stage to isolate documents from different stages. Each stage can only edit documents within its own stage. The project document list in the "Plan Document" needs to be configured with a corresponding docId based on the document name to enable the function of opening the corresponding document by clicking on the document name.

[0198] The `syncProjectDirectory` public method is called to handle the project folder synchronization logic, which is used for viewing project folders on the project collaboration page. The relevant rules have been explained in detail above.

[0199] The public method syncTestReportPrototypeNumber is called to process the sample table rows of the test report. The relevant rules have been explained in detail above.

[0200] Based on the current document data, update the `existPackageSample` and `nowPhaseExistBudget` attributes and save the results to the `pp_phase_hand_over_num` data table. The rules for the two attributes are as follows: `existPackageSample` value rule: 0 represents no packaging / poster sample production, 1 represents packaging / poster sample production, used to determine whether the non-conforming delivery termination process can be initiated when the client's acceptance fails; `nowPhaseExistBudget` value rule: 0 represents no budget in the current stage, 1 represents a budget in the current stage, used to determine whether the budget content block is displayed or hidden.

[0201] Based on the overall work schedule data in the "Plan Document", generate the task document for the current stage and save it to the pp_doc_task data table for displaying the task document button and its corresponding status on the front end; at the same time, update the deliverable field isDeliver of the corresponding document in the pp_phase_doclib data table to a value of 1, which indicates that the document needs to be delivered in the current stage.

[0202] Extract all test report documents and complete the cell content configuration for the corresponding test report document name and version.

[0203] If there are logistics documents to be delivered in the next stage, copy the logistics content block and increment the delivery count corresponding to the logistics title by 1.

[0204] Complete the progress bar node status processing: Change the processCompleteStatus field of the previous node to COMPLETE (corresponding to a black process line displayed on the front end), change the node status field nodeCompleteStatus of the current node to COMPLETE (corresponding to a black node displayed on the front end), change the processCompleteStatus field of the current node to ON_GOING (corresponding to a green process line displayed on the front end), record the completion time of the current node, and change the node status field nodeCompleteStatus of the next node to ON_GOING (corresponding to a green node displayed on the front end).

[0205] The `projectOverdueRate` public method is called to calculate the current project's overdue rate; this method has been explained in detail above. The `modifyPhaseNodePostponementTime` public method is called to update the estimated completion time of the progress bar; this method has been explained in detail above.

[0206] After acceptance, the project enters the next phase, and document permissions for the next phase must be allocated according to the following rules: (1) For Party A, Party A has viewing permission for its own task documents and needs to set the docView attribute to true; if the project is a graduation project, Party A has viewing permission for all other documents and needs to set the docView attribute to true; if it is not a graduation project, Party A does not have viewing permission for other documents and needs to set the docView attribute to false.

[0207] (2) For the person in charge of Party B, the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties should be set to true for the documents to be delivered to Party B’s own personnel and the personnel under management; the docView property should be set to true for the invoice documents that do not need to be delivered to Party B’s own personnel and the personnel under management; and the docView, docEdit, and leaderConclusionHeader properties should be set to true for the non-invoice documents that do not need to be delivered to Party B’s own personnel and the personnel under management.

[0208] (3) For project team members, if the team member's permissions have been taken over, the team member can only view all documents and the docView property should be set to true; if the team member's permissions have not been taken over, for the documents that the team member belongs to and need to deliver, the docView, docEdit, leaderConclusion, and leaderConclusionHeader properties should be set to true; for the invoice documents that the team member belongs to and do not need to deliver, the docView property should be set to true; for the non-invoice documents that the team member belongs to and do not need to deliver, the docView, docEdit, and leaderConclusionHeader properties should be set to true.

[0209] Reset the contents of the cells corresponding to Party B's conclusions and Party A's acceptance in all task documents.

[0210] After the client's acceptance process is completed, delete the scheduled task for "Overdue Acceptance".

[0211] If the project proposal phase passes acceptance, and new items required by the client are added during the proposal phase, the project will enter the client-provided items phase after acceptance. The following operations must be performed: Start the scheduled task "[Client has not provided items on time]"; set the `existPartyAProvideMaterial` attribute to 1 (1 indicates that client-provided items exist in the project), the `isPartyAProvidePhase` attribute to 1 (1 indicates that the project is currently in the client-provided items process), and the `partyAHandOverToPartyB` attribute to 1 (1 indicates that client-provided items are being compiled); create a new client-provided items task document and configure the operation permissions for each project member; save the client-provided items event and its corresponding start time to the `pp_event_record` data table to identify when the project enters the client-provided items process after acceptance. If the above conditions are not met, configure the opposite attribute values ​​and document permissions, and do not start the corresponding scheduled task.

[0212] After acceptance, delete the document data from the previous stage. For example, if the project enters the third stage after the client's acceptance in the first stage, the document data from the first stage needs to be deleted.

[0213] The syncInvoiceDocExcerptAmount public method is called to synchronize the budget amounts for each position. This method has been explained in detail above.

[0214] The invoice summary is a common method logic, which will only be explained here and will not be elaborated on later: It calls the projectSummaryInvoice common method to extract all invoice documents for the current project, reads the budget amount and user-filled content from the invoice documents, and configures the user-filled content into the corresponding position in the "Project Outsourcing Invoice Expense Statistics Summary Table" document.

[0215] For all logistics documents in the next phase, set the editable attribute based on whether logistics days are configured, thereby controlling the editability of the third-party logistics radio button.

[0216] If the phase after acceptance is the final phase of the project, the cooperateContent attribute should be set to DOCUMENT (to indicate that the current acceptance phase is partial) and saved to the pp_phase_cooperate_status data table; if the project enters the final phase and the "Packaged Samples Available" radio button has been selected in the "Requirements" document, the packaged sample content block in the test report document should be configured to be displayed.

[0217] Finally, the front-end is notified via web-socket to update the project collaboration page and document page in real time, triggering a to-do notification sound, and simultaneously calling the WeChat API to send WeChat notifications to the corresponding users.

[0218] The following is a partial acceptance process in one embodiment: For Party A to activate the "Partial Acceptance Passed" button, the following conditions must be met simultaneously: Party A has completed the acceptance of all non-source documents delivered by Party B, and the acceptance conclusion of Party A for all non-source documents is "passed", and the current time is within the working hours.

[0219] Query the pp_phase_cooperate_status data table, read the value of the cooperation status attribute cooperationStatus, and verify whether the current cooperation status is equal to CAN_ACCEPTANCE_PASS (i.e., the acceptance status is passed).

[0220] If the acceptance is not completed within the specified period, it will be considered as accepted by default. In this case, the "Acceptance passed by default, no information to fill in" text should be entered in the "Communication Record Form" in the column for Party B where no information is to be filled in.

[0221] After partial acceptance, the project enters the source file acceptance phase, and document permissions must be assigned according to the following rules: (1) For Party A, for all source files, the docView, partyAAcceptanceCheck, and partyAAcceptanceCheckHeader properties must be set to true; for the remaining files, the docView property must be set to true.

[0222] (2) For the person in charge of Party B and project team members, the docView property should be set to true for all task documents.

[0223] Increment the number of acceptances by Party A by 1, set the assessTipsFlag and acceptanceAssessFirstTipsFlag properties to 0, and reset the number of deliveries, acceptances, and other related properties.

[0224] Modify the cooperateContent attribute in the pp_phase_cooperate_status data table to SOURCE_FILE (to indicate that the current stage is the source file acceptance phase during the client's acceptance process).

[0225] Change the collaboration status between Party A and Party B's responsible persons to DOCUMENT_ACCEPTANCE (i.e., document acceptance) to indicate that the project is currently in the acceptance phase by Party A.

[0226] Save the process records of the partial acceptance by Party A, and update the profile picture area and pending items messages.

[0227] If there is a process for the client to return items in some acceptance stages, but there is no process for the client to return items after entering the source document acceptance stage, then set the existPartyAReturnPhase property to 0 (0 means there is no process for the client to return items).

[0228] Record partial acceptance events and their corresponding times, as well as source document acceptance events and their start times, for use in project-related time calculations.

[0229] Delete the scheduled task "Overdue Partial Acceptance" and start the scheduled task "Overdue Source File Acceptance".

[0230] Finally, the front-end is notified via web-socket to update the project collaboration page and document page in real time, triggering a to-do notification sound, and simultaneously calling the WeChat API to send WeChat notifications to the corresponding users.

[0231] The following is a process for source file acceptance in one embodiment: For Party A to activate the "Source File Acceptance Passed" button, the following conditions must be met simultaneously: Party A has completed the acceptance of all source files delivered by Party B, and Party A's evaluation conclusion for all source files is "passed," and the current time is within the working hours.

[0232] Query the pp_phase_cooperate_status data table, read the value of the cooperation status attribute cooperationStatus, and verify whether the current cooperation status is equal to CAN_ACCEPTANCE_PASS (i.e., the acceptance status is passed).

[0233] If the acceptance is not completed within the specified period, it will be considered as accepted by default. In this case, the "Acceptance passed by default, no information to fill in" text should be entered in the "Communication Record Form" in the column for Party B where no information is to be filled in.

[0234] After acceptance, configure the "Communication Record Form": If a cell in the Party A column or the Party B column of a certain row already contains content, set the editable attribute of all cells in that row to false, that is, set it to an uneditable state, and the content is recorded as history and cannot be modified.

[0235] Increment the number of acceptances by Party A by 1, set the assessTipsFlag and acceptanceAssessFirstTipsFlag attributes to 0, and save the data to the pp_phase_hand_over_num table.

[0236] Save the process record of the acceptance of the source files from Party A, and update the profile picture area and pending task messages.

[0237] Once the source files have been accepted, the project is officially completed, and the scheduled tasks for "Overdue Unaccepted Source Files" and "Overdue Undelivered" need to be deleted.

[0238] Update progress bar node status: Change the node status field nodeCompleteStatus of the project completion node to COMPLETE (corresponding to the black node displayed on the front end), record the time of the project completion node, and change the process line field processCompleteStatus of the previous node to COMPLETE (corresponding to the black process line displayed on the front end).

[0239] Once the project is completed, document permissions should be assigned according to the following rules: (1) For Party A, the docView, partyAAssessHeader, and partyAAcceptanceCheckHeader properties must be set to true for all documents.

[0240] (2) For the person in charge of Party B, the docView and leaderConclusionHeader attributes should be set to true for the documents belonging to the person in charge of Party B and the documents of the team members being taken over, and no permissions should be assigned to the other documents.

[0241] (3) For project team members, the docView and leaderConclusionHeader attributes should be set to true for the documents to which the team member belongs, and no permissions should be assigned to other documents.

[0242] Change the project status attribute projectStatus to COMPLETE_COOPERATE (i.e., project completed), change the project phase attribute phase to COOPERATE_SUCCESS (i.e., project completed), and save the actual project completion time to the pp_project data table.

[0243] Modify the projectPhase attribute of this project in all relevant database tables to COOPERATE_SUCCESS (i.e., project completion). The modification covers the corresponding content of this project in the database tables such as pp_phase_cooperate_message (avatar area information table), pp_project_doc_permission (document permission table), pp_doc_task (task document table), pp_phase_doclib (project folder table), and dt_document (project document table).

[0244] Upon project completion, project outcome display images need to be stored: According to platform rules, extract the image upload controls with the projectPresentation attribute set to true from the document, and store the outcome display images for the corresponding positions in the pp_project_member database table for use in the project completion list to display outcome images.

[0245] After the project is completed, the corresponding documents are located based on dt_doc_material_record (material entry record form) and dt_doc_literature_record (literature entry record form), and the materials and documents registered in the documents are checked to see if they have actually been used. For materials and documents that have not been used, the corresponding entries in the documents are cleared and their usage count is decremented by 1.

[0246] Upon project completion, all materials originating from "Designer's Design" and their associated content must be migrated to the Client's private database, with the manufacturer attribute set to "Made in-house," marking the transfer of ownership of the material to the Client. If the same material is found to already exist in the Client's private database during the migration process, that material will be skipped, and the migration operation will not be performed.

[0247] Configure the project completion notification to allow users to view project completion details. If any team members leave their positions or the project during the collaboration process, the relevant fees and credit score data must be imported into the corresponding exit record. The platform will then use the project completion notification to settle fees and calculate credit scores for project members.

[0248] Delete all scheduled tasks for this project. Once the project is completed, the business logic processing of the scheduled tasks for this project will no longer be executed.

[0249] Finally, the frontend is notified via WebSocket to update the project collaboration page and document page in real time and trigger a to-do notification sound. At the same time, the WeChat API is called to send WeChat notifications to the corresponding users. In one embodiment, the method further includes: S109.

[0250] S109. Before the target project enters the delivery phase by Party B, start the preset timed task.

[0251] The preset scheduled tasks include overdue delivery tasks and work period reminder tasks. Overdue delivery tasks are used to calculate the overdue rate of the target project and deduct overdue payments. Work period reminder tasks trigger real-time page updates on the project collaboration platform at the start and end times of each progress stage of the target project.

[0252] In one embodiment, the method further includes: S110.

[0253] S110. If the planning document is changed, the progress of the target project is set to the in-progress stage, and a new target document is generated based on the changed planning document.

[0254] It should be noted that S110 has been described in detail in the above embodiments. Therefore, it will not be repeated here.

[0255] In one embodiment, the B party includes the B party's representative and B party's team members, and the above S103 specifically includes the following steps: S1031. In response to a task conclusion editing request from a member of Party B's team, edit Party B's task conclusion in at least one task document and submit it to Party B's responsible person; S1032. In response to the review request from the person in charge of Party B, review the conclusions of Party B's task; S1033. If the task conclusion of Party B is approved, then the task conclusion of Party B shall be submitted.

[0256] It should be noted that S1031-S1033 have been described in detail in the above embodiments. Therefore, they will not be repeated here.

[0257] In one embodiment, the at least one task document includes a target task document, and the method further includes: S111.

[0258] S111. If the client's acceptance conclusion for the target task document is "not approved", a preset communication record form will be displayed on the project collaboration platform.

[0259] The pre-set communication record form is used to facilitate communication between Party A and Party B.

[0260] It should be noted that the preset communication record form is the aforementioned "Communication Record Form". This application will not elaborate further on this point.

[0261] In this embodiment, the activation conditions for the project termination option initiated by Party A are as follows: The activation of all project termination options must meet the prerequisite condition: the current process is not within the process of Party A providing items. (1) Termination of cooperation option due to reasons of Party A: This termination option has the lowest activation priority and is activated only when other termination options are not activated, the project is not in the final stage, and the logistics of the goods delivered by Party B are not in progress.

[0262] (2) Termination option if Party A is not satisfied with Party B's delivery: This termination option will be activated when the following conditions are met, and Party A has completed the second or more acceptances in the current stage, and the acceptance page displays the "Acceptance Failed" button: the first two stages of a three-stage creative design project, the first stage of a two-stage creative design project, the first two stages of a five-stage smart hardware project, or other types of projects.

[0263] (3) Termination of cooperation due to serious overdue period of Party B: This termination option is activated when Party B's overdue rate reaches Y2; this option has the highest activation priority and can be activated at the same time as other termination options.

[0264] (4) Termination of cooperation option due to Party A's determination that Party B's delivery is unqualified: This termination option will be activated when all of the following conditions are met: Party A has completed the second or more acceptances in the current stage, the acceptance page displays the "Acceptance Failed" button, the status of the whole machine test report document is "Acceptance Failed", and Party A has not completed the "Returned Items" document.

[0265] (5) Termination of cooperation option due to the client's determination that the source file is unqualified: When the project is in the final stage and the client is accepting the source file, and the client has completed the second or more acceptances in the current stage, and the acceptance page displays the "Acceptance failed" button, this termination option is activated.

[0266] In one embodiment, this application first verifies the following conditions: the current user is Party A, the project is in progress, and Party A has not completed the "Returned Items" document.

[0267] Modify the project status attribute projectStatus in the pp_project database table to START_COOPERATE_TERMINATED to indicate that the project is in the start-up and termination process; at the same time, store the termination type attribute terminatedType for subsequent business logic to use.

[0268] Query the pp_phase_cooperate_message database table, back up and copy the current avatar area message data, and set the dataStatus attribute of the backup data to BEFORE_RECOVERY so that when the client resumes cooperation, the avatar area messages can be restored to the state before termination.

[0269] If Party A initiates termination for the first time under the same termination type, the project enters a cooling-off period, and the "Cooling-off Period Countdown" timed task is started to record the start and termination events for use in project-related time calculations.

[0270] If this is the second termination under the same termination type: If the termination reason is unqualified deliverables or unqualified source documents, the project enters the dispute period, and the "Dispute Period Countdown" scheduled task is started; if the termination reason does not fall into either of the above two categories, it is necessary to determine whether the client provided any items during the project execution: If the client provided any items, the project status is changed to PROJECT_SUSPENDED, a "Return by Party B" or "Return by Party A" task document is generated, operation permissions for this document are assigned to project members, and the project enters the suspended phase; if the client did not provide any items during the project execution, the project is terminated directly, the project termination reason is stored, the project status and related data are updated to COOPERATE_TERMINATED, a project termination notice is generated, the project is closed according to the notice, the usage of materials and documents is determined based on the document content and the number of times they are used is processed accordingly, and all scheduled tasks for the project are deleted.

[0271] Progress bar node processing rules: Insert start / end nodes and project termination nodes, and store the start / end node times; if it is the second start / end and the project terminates directly, set the project termination node time and set the node status nodeCompleteStatus to COMPLETE (the front-end node is displayed in black); otherwise, do not set the termination time and set the node status nodeCompleteStatus to ON_GOING (the front-end node is displayed in green).

[0272] Store the process record of the project termination initiated by Party A, and update the messages in the avatar area and the messages in the to-do list.

[0273] If project termination is initiated during the acceptance period, the end time of the acceptance overdue event or acceptance event will be updated for use in project-related time calculations.

[0274] Ultimately, the front-end is notified via web-socket to update the project collaboration page and document page in real time, and to trigger a to-do notification sound; at the same time, the WeChat API is called to send WeChat notifications to the corresponding users.

[0275] In one embodiment, the display rules for the "Disagree to Terminate" button are as follows: the current termination reason is that Party A proposes termination because Party B's deliverables are unqualified, or Party A proposes termination because Party B's source documents are unqualified, and the project status is in the start-up termination stage or the project is in the cooling-off period, and the current user is Party B's project manager.

[0276] Call the noAgreeTerminationProject interface to validate the following conditions: currently within working hours, project in the start / terminal phase, in a cooling-off period, and the current user is the project manager of Party B.

[0277] After verification, the project enters the dispute period. The system deletes the "cooling-off period countdown" scheduled task and starts the "dispute period countdown" scheduled task.

[0278] After changing the cooperateTerminatedStatus attribute to DISPUTEPERIOD and saving it to the pp_project database table, it indicates that the project has entered the dispute period.

[0279] Retrieve startup and termination events from the pp_event_record database table and set the cool-off period end time for each event.

[0280] Save the operation record of Party B's disagreement with termination, and update the profile picture area and to-do items messages.

[0281] Finally, a notification is sent to the front end via web-socket to complete the real-time update of the project collaboration page and document page, trigger the to-do notification sound, and call the WeChat API interface to push WeChat notifications to the corresponding users.

[0282] In one embodiment, the "Agree to Terminate" button is displayed as follows: the current project status is in the start-up / termination phase, and the current user is the project manager of Party B.

[0283] Call the agreeTerminationProject interface to validate the following conditions: currently within a working period, project in the start-up / termination phase, and the current operator is the project manager of Party B.

[0284] The termination type and termination reason are saved to the pp_project database table for use in configuring termination reasons in the document, and for displaying termination reasons in the project list.

[0285] Save the operation record of Party B's agreement to terminate, and update the profile picture area and to-do items messages.

[0286] If you agree to terminate the agreement during the cooling-off period, delete the "Cooling-off Period Countdown" timed task; otherwise, delete the "Dispute Period Countdown" timed task.

[0287] Determine whether Party A provided any items during the project execution process: If Party A provided any items, and Party B agrees to terminate the project, the project status will be changed to PROJECT_SUSPENDED, and a task document titled "Party B Returns" or "Party A Returns Goods" will be generated. Permissions for this document will be assigned to project members. The relevant rules have been described in detail above, and the project will enter the suspended phase.

[0288] If Party A has not provided any items, Party B agrees to terminate the project directly upon termination. The project status and related data will be updated to COOPERATE_TERMINATED, a project termination notice will be generated, and the project will be closed according to the notice. The usage of materials and documents will be assessed based on the document content, and the corresponding usage frequency will be adjusted accordingly. All scheduled tasks for the project will be deleted. The document viewing permission configuration rules after project termination are as follows: (1) Termination initiated during acceptance: If the termination occurs during the source file acceptance period, Party A can view all document content, and the corresponding docView property is set to true; if the termination occurs during the partial acceptance period, for graduation project projects, the source files are open to Party A for viewing, and the docView property is set to true; for non-graduation project projects, viewing is not open, and the docView property is set to false; all other documents are open for viewing, and the docView property is set to true; if the termination occurs during the normal acceptance period, documents that have been delivered and do not need to be delivered again, documents delivered in the current stage, "Requirements", "Solutions", "Plans", and "Items Provided by Party A" documents are open for viewing, and the docView property is set to true; for other documents, if they are graduation project projects, viewing is open, and the docView property is set to true; for non-graduation project projects, viewing is not open, and the docView property is set to false.

[0289] If the termination is initiated by Party B during the delivery process: If the termination occurs during the delivery of source files, for graduation project-type projects, the source files will be open to Party A for viewing, with the docView attribute set to true; for non-graduation project-type projects, the source files will not be open for viewing, with the docView attribute set to false; all other documents will be open for viewing, with the docView attribute set to true. If the termination occurs outside the delivery period of source files, documents that have been delivered and do not need to be delivered again, documents delivered in the current stage, and documents such as "Requirements," "Proposals," "Plans," and "Items Provided by Party A" will be open for viewing, with the docView attribute set to true; for other documents, if they are graduation project-type projects, they will be open for viewing, with the docView attribute set to true; for non-graduation project-type projects, they will not be open for viewing, with the docView attribute set to false.

[0290] (2) For the person in charge of Party B, the document viewing permission for himself and the team members under his management is enabled, and the docView property is set to true. The viewing permission for other documents is disabled, and the docView property is set to false.

[0291] (3) For project team members, the docView property is set to true for their own documents and not for other documents.

[0292] In the document configuration, add the text "Project terminated, not filled in" to the blank "Party B" column in the "Communication Record Form".

[0293] Finally, a notification is sent to the front end via web-socket to complete the real-time update of the project collaboration page and document page, trigger the to-do notification sound, and call the WeChat API interface to push WeChat notifications to the corresponding users.

[0294] In one embodiment, the current project status is verified to confirm that the project has entered the project termination and startup phase corresponding to START_COOPERATE_TERMINATED.

[0295] If the current period is a cooling-off period, delete the cooling-off period scheduled task; otherwise, delete the dispute period scheduled task.

[0296] If a third-party testing project has been published when the project is in the termination phase, the published project will be automatically stopped from being published and cannot be republished. The status of the third-party testing project needs to be changed to the STOP_USED state, and the thirdPartyNextStepFlag attribute should be changed to 0. The "Next" button of the relevant third-party testing project will be hidden.

[0297] Delete the avatar area messages generated during the project termination phase, change the avatar area messages that were saved before the project termination and whose dataStatus attribute was BEFORE_RECOVERY to CURRENT, and restore the avatar area messages that were in progress before the project termination.

[0298] Process the progress bar nodes as follows: Change the processCompleteStatus of the terminated start node to COMPLETE (the front-end process line is displayed in black); change the terminated cooperation node to the resumed cooperation node, set the node time, set the nodeCompleteStatus of the node to COMPLETE (the front-end node is displayed in black), and set the processCompleteStatus of the process line to ON_GOING (the front-end process line is displayed in green); after resuming cooperation, change the nodeCompleteStatus of all nodes to ON_GOING (the front-end node is displayed in green).

[0299] Change the projectStatus property to PROGRESS to indicate that the project is currently in progress; clear the thirdPartyReleaseProjectId property to restore the entrustTestStatus status to the pending test status corresponding to WAIT_ENTRUST_TEST to avoid affecting subsequent business logic.

[0300] If the resumption of cooperation is triggered by a "qualified" conclusion issued by a third-party testing project, then set the corresponding attribute noStartDeliveryFailTerminated or noStartSourceFileFailTerminated to restrict the current stage from restarting the same type of termination option.

[0301] Update the end time of the termination startup event for use in project-related time calculations.

[0302] If the project was in the acceptance phase before termination, the scheduled task for "Overdue Acceptance" will continue to be calculated based on the state before termination after the cooperation is resumed.

[0303] Save the process record of Party A's resumption of cooperation, and update the profile picture area and to-do items.

[0304] The `projectOverdueRate` public method is called to calculate the current project's overdue rate. See above for details.

[0305] The estimated completion time of the progress bar is updated by calling the public method modifyPhaseNodePostponementTime. See above for details.

[0306] Finally, a notification is sent to the front end via web-socket to achieve real-time updates of the project collaboration page and document page, trigger a to-do notification sound, and simultaneously call the WeChat API to push WeChat notifications to the corresponding users.

[0307] In one embodiment, this application can support publishing third-party testing projects and entrusting third parties to carry out testing work. The specific rules are as follows: when a project is in the termination dispute period, the remaining dispute period days are greater than the configured remaining dispute period days, and the entrustTestStatus test status is the pending test status corresponding to WAIT_ENTRUST_TEST, Party A can click the "Entrust Third-Party Testing" button to publish a third-party testing project and entrust a third party to carry out testing.

[0308] After a third party tests the prototype, sample, software, or source files of the source project, and issues a conclusion on whether it is qualified, Party A may choose to terminate the source project cooperation or continue the source project cooperation based on the conclusion.

[0309] In one embodiment, the overdue rate of the target project is calculated using the following formula: , ,

[0310] in, This refers to the actual number of days worked by Party B. The total number of days planned for the project. The actual working time of Party B. This refers to the total working time of Party B. This is an extension of the employee's working hours. The time during which Party A inspects and provides materials during Party B's working hours.

[0311] In one embodiment, the method further includes: S112-S114.

[0312] S112. If the overdue rate of the target project is greater than or equal to the first preset threshold, and the overdue rate of the target project is less than the second preset threshold, then the deduction operation is performed on the target project. S113. If the overdue rate of the target project is greater than or equal to the second preset threshold, and the overdue rate of the target project is less than the third preset threshold, then activate the project termination option on the project collaboration platform. S114. If the overdue rate of the target project is greater than or equal to the third preset threshold, the full amount of the target project will be deducted and the target project will be terminated.

[0313] It should be noted that S112-S114 will be explained in detail below.

[0314] In one embodiment, during the project execution phase, regardless of the project's current interval, corresponding day limits and overdue calculation rules are set. When the overdue days reach the corresponding node, the corresponding business logic is triggered; the overdue period is calculated in working days.

[0315] In the project collaboration process, different work stages are set with a fixed number of working days. Stage overdue refers to the situation where the actual number of working days consumed in a stage exceeds the planned fixed number of working days for that stage.

[0316] For projects that are not single-phase projects, if a phase exceeds the deadline and the overall project is within the deadline, the number of days the phase is overdue will be displayed in the area of ​​the contractor's avatar on the project collaboration page.

[0317] The project overdue status is determined by calculating the project overdue rate formula. The number of working days required to reach the overdue rate can be deduced from the target project overdue rate. Then, the corresponding timestamp is determined based on the number of working days, and the corresponding business logic is triggered by the timer when the timestamp is reached.

[0318] The formula for calculating the project overdue rate is as follows: (1) The actual working time of Party B = Working time of the working period - Extended time of the working period - First acceptance time of Party A during the working period - First delivery time of goods and logistics time of Party A during the first stage of the working period (2) Actual number of working days of Party B = Actual working time of Party B / (Percentage of working time per day × Time allocated per day) (3) Project overdue rate = (Actual working days of Party B - Total planned days) / Total planned days The actual number of working days required to trigger a project to start being overdue is (1 + 0.01) × the total number of days planned by Party B. When a project enters an overdue state, the system updates the avatar area and to-do items messages, and starts displaying the project overdue rate data in the avatar area of ​​Party B's person in charge on the project collaboration page.

[0319] For graduation project projects, if the total planned number of days is greater than 200 days, Y1 is -0.1; otherwise, Y1 = -((a - (b × total planned number of days)) / 100). For non-graduation project projects, Y1 = a - (b × total planned number of days by Party B), where a and b are system configuration coefficients.

[0320] The number of working days required for a project's overdue rate to reach Y1 = (Y1 + 1) × planned days. When the project's overdue rate reaches Y1, the system updates the avatar area and to-do items, and initiates the project payment deduction process. It should be noted that Y1 is the first preset threshold.

[0321] When the project overdue rate reaches Y2, where Y2 = coefficient × Y1, the number of working days required to reach Y2 is (Y2 + 1) × planned days. When the project overdue rate reaches Y2, the system updates the avatar area and to-do items, determines that the contractor is seriously overdue, and activates the project termination option. It should be noted that Y2 is the second preset threshold.

[0322] When a project's overdue rate reaches Y3, where Y3 is 0 for graduation project projects and Y3 = coefficient × Y1 for non-graduation project projects, the number of working days required for the project's overdue rate to reach Y3 is (Y3 + 1) × planned days. If a graduation project is in the change phase and the overdue rate reaches Y3, it is necessary to determine whether the countdown value of the original plan's near-term termination before the change is greater than 0. If it is greater than 0, the change is cancelled, and the project continues according to the original plan before the change; otherwise, the project is terminated directly. It should be noted that Y3 is the third preset threshold.

[0323] When the overdue rate of other types of projects reaches Y3, it is determined that Party B has seriously overdue the delivery, the full amount of the project payment will be deducted, and the project will be automatically terminated. The business logic is consistent with the project termination rules in Section 4.4.

[0324] For graduation project projects, the client's profile picture area will not display the project overdue rate or deduction data. The project termination countdown will be displayed at the top of the project collaboration page, with the background color dynamically changing according to the countdown progress.

[0325] In one embodiment, the rules for the client's acceptance of goods beyond the deadline are explained below.

[0326] The number of working days required to trigger the start of overdue period = (number of days × a) + (number of days × a) × b, where the coefficient a is 1 during normal acceptance period, 0.7 during partial acceptance period, and 0.3 during source file acceptance period; the coefficient b corresponding to the start of overdue period is configured by the backend, and its current value is 0.

[0327] Example: If Party A is in the normal acceptance period and the current acceptance period is 10 days, then the number of working days required to trigger the start of overdue period is 10 days; if Party A is in the partial acceptance period and the current acceptance period is 10 days, then the number of working days required to trigger the start of overdue period is 7 days.

[0328] When the expiration date is reached, the system saves the operation record of the expiration process and updates the avatar area and to-do items.

[0329] The number of working days required to trigger a serious overdue period = (number of days × a) + (number of days × a) × b, where the coefficient a is 1 during normal acceptance, 0.7 during partial acceptance, and 0.3 during source file acceptance; the coefficient b corresponding to serious overdue period is configured by the backend and is currently set to 0.8.

[0330] Example: If Party A is in the normal acceptance period and the current acceptance period is 10 days, then the number of working days required to trigger serious overdue period is 18 days; if Party A is in the partial acceptance period and the current acceptance period is 10 days, then the number of working days required to trigger serious overdue period is 12.6 days.

[0331] When the system reaches the critical overdue point, it saves the operation record of the critical overdue process and updates the avatar area and pending items.

[0332] The number of working days required to trigger the MAX overdue period is calculated as (number of days × a) + (number of days × a) × b, where the coefficient a is 1 during normal acceptance, 0.7 during partial acceptance, and 0.3 during source file acceptance. The coefficient b corresponding to the MAX overdue period is configured by the backend and is currently set to 1.

[0333] Example: If Party A is in the normal acceptance period and the current acceptance period is 10 days, then the number of working days required to trigger the MAX overdue period is 20 days; if Party A is in the partial acceptance period and the current acceptance period is 10 days, then the number of working days required to trigger the MAX overdue period is 14 days.

[0334] When the MAX node is reached, the system executes the acceptance logic in section 3.4.

[0335] In one embodiment, the following describes the cooling-off period and dispute period countdown rules for project termination.

[0336] Once the project enters the cooling-off period, the system will start a countdown timer task for the cooling-off period. The number of countdown days is configured in the backend and is calculated based on working days.

[0337] If the project is terminated due to unqualified deliverables or source documents after the countdown ends, the project will enter the dispute period; otherwise, the project will be terminated directly, the system will save the process operation record of the end of the cooling-off period countdown, execute the termination business logic, and the project will be closed in accordance with the content of the termination notice.

[0338] If the cooling-off period countdown ends, or Party B clicks the "Disagree to Terminate" button, or Party A initiates a second termination request of the same type, the project enters the dispute period. The system will then start a timed task to count down the dispute period. The number of countdown days is configured in the backend and is calculated based on working days.

[0339] During the dispute period, Party A may publish third-party testing projects and entrust third parties to carry out testing.

[0340] If Party A fails to provide a third-party testing report after the countdown of the dispute period ends, the system will save the process operation record of the end of the dispute period countdown, terminate the project, and complete the project closure in accordance with the contents of the termination notice.

[0341] In one embodiment, the rules for logistics delays are described below.

[0342] The maximum logistics overdue time is calculated as: the number of days of logistics reported × a coefficient. The current logistics overdue coefficient configured in the backend is 2.

[0343] When Party B delivers goods or Party A returns goods, Party B selects a third-party logistics provider and fills in the tracking number. If the logistics status is "not signed for," the platform will subscribe to the logistics progress from the third-party logistics API based on the tracking number and simultaneously start a timed task for overdue logistics.

[0344] If the logistics delay reaches the MAX threshold and the third-party logistics provider does not notify the recipient of the tracking number during the delay, the logistics is considered to have been delivered and the project continues. The delay in logistics is included in the project extension time and does not affect the determination of project stage delay or the calculation of project delay rate.

[0345] In one embodiment, the relevant algorithms involved in project collaboration are described below.

[0346] Overdue deductions: Once the project overdue rate reaches Y2, the project payment deduction process will be initiated.

[0347] Overdue deduction for positions = Total cost of personnel in the position × ((Actual overdue rate Y - Overdue rate of projects that started deduction Y1) / 2 × Overdue rate of projects that started deduction Y1) The overdue deduction for an employee is the sum of the overdue deductions for all positions held by that employee.

[0348] Project cost calculation: For projects where the source files have passed acceptance and the project is completed, the project settlement fee will be equal to the agreed-upon project fee. For projects where cooperation is terminated, the corresponding settlement fee will be calculated based on the reason for termination, as shown in the example below: (1) The first phase of the project was stopped and terminated due to reasons attributable to Party A. The settlement fee for the position = (total position fee - overdue position deduction - outsourcing position budget) × weight of the first phase of Party A's project termination + total outsourcing budget up to the current phase - refund amount of outsourcing budget settlement. The project settlement cost is the sum of the settlement costs for each position. (2) If the overdue rate reaches Y3, the full amount will be deducted, and the project settlement fee will be 0. Working days calculation: Working days are calculated using the WORKTIME function, with the format: WORKTIME(start time, number of working days, weekend / holiday indicator, holiday / day adjustment array). Example: A start time of 1767571200000 milliseconds corresponds to 08:00:00 on Monday, January 5, 2026. The weekend / holiday indicator is 1, representing Saturdays, Sundays, and public holidays. The working period is from 08:00:00 to 18:00:00. The current time is 1768384800000 milliseconds, corresponding to 18:00:00 on Wednesday, January 14, 2026. Substituting these values ​​into the WORKTIME function, we can deduce that the project has 8 working days from the start time to the current time.

[0349] In one embodiment, during project collaboration, project members can click the file button on the document editing page to select and export the current document or all documents within their permissions for the project. The exported file format is PDF. During the project collaboration between Party A and Party B, not all personnel have the permission to export all project documents; different export permissions are set for different personnel for different documents at different stages.

[0350] In one embodiment, during project collaboration, different task documents are assigned to personnel at different stages and in different positions. The project's task document page only displays the task documents belonging to each project member, along with the document's name, status, operation buttons, document collaboration, and real-time communication status data. Project members can click on the document button or document name to navigate to the document editing page to edit the content. The document status is updated in real-time based on user actions and document content.

[0351] In one embodiment, the project folder displays the project's change history, legacy files, files before the change, and the contents of currently effective files. It also includes the name, modification date, type, and size of each file. Users can click on the document name to jump to the document editor page to view and modify it.

[0352] In one embodiment, if the project has completed the requirement change, the system displays a list of change record options. After clicking, the user can view the completed negotiations, the changed requirements, the plan, the "Plan Document", and the change-related invoice documents, which can be used by the user to query, compare and refer to the change-related document content.

[0353] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0354] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0355] The steps in the methods of this application embodiment can be adjusted, merged, or deleted according to actual needs. The units in the apparatus of this application embodiment can be merged, divided, or deleted according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0356] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0357] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0358] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Since these modifications and variations fall within the scope of the claims and their equivalents, this application also intends to include these modifications and variations.

[0359] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.< / phasedoclibpo> < / file> < / file>

Claims

1. A project collaboration method, characterized in that, The method is applied to a project collaboration platform, and the method includes: Once the target project enters the in-process phase, obtain the project's planning document; Initialize the target document corresponding to the ongoing stage according to the plan document, wherein the target document includes at least one task document; After the target project enters the delivery phase by Party B, in response to Party B's request to edit the task conclusion, Party B edits and submits the task conclusion of each task document in the at least one task document; Calculate the document pass rate based on the conclusion of the B party's task in each of the at least one task document; If the document pass rate is greater than the first preset threshold, the progress of the target project will be set to the client acceptance stage and the client will be notified. After the target project enters the client acceptance phase, in response to the client's acceptance request, the client's acceptance conclusion for each of the at least one task document is edited and submitted. Calculate the acceptance pass rate based on the client's acceptance conclusion for each of the at least one task documents; If the acceptance pass rate is greater than the second preset threshold, the target project is deemed to have passed acceptance.

2. The method according to claim 1, characterized in that, The initialization of the target document corresponding to the ongoing stage based on the plan document includes: Based on the overall work schedule data in the plan document, generate the at least one task document.

3. The method according to claim 1, characterized in that, The target document also includes a configuration and calculation data document and a notification document. The initialization of the target document corresponding to the ongoing phase based on the plan document includes: Extract job information from the aforementioned planning document; The job information will be synchronized to the corresponding job information in the configuration and calculation data document and the notification document.

4. The method according to claim 1, characterized in that, The method further includes: Before the target project enters the delivery stage by Party B, a preset timed task is initiated. The preset timed task includes an overdue delivery timed task and a work period reminder timed task. The overdue delivery timed task is used to calculate the overdue rate of the target project and the overdue deduction. The work period reminder timed task is used to trigger a real-time update notification on the project collaboration platform at the start and end times of each progress stage of the target project.

5. The method according to claim 1, characterized in that, The method further includes: If the planning document is changed, the progress of the target project is set to the in-progress stage, and a new target document is generated based on the changed planning document.

6. The method according to claim 1, characterized in that, The second party includes the person in charge of the second party and the members of the second party's team. The step of responding to the second party's task conclusion editing request, editing and submitting the second party's task conclusion for each task document in the at least one task document, includes: In response to the task conclusion editing request from the member of Party B, the task conclusion of Party B is edited in the at least one task document and submitted to the person in charge of Party B; In response to the review request from the person in charge of Party B, the task conclusion of Party B shall be reviewed; If the task conclusion of Party B is approved, then the task conclusion of Party B shall be submitted.

7. The method according to claim 1, characterized in that, The at least one task document includes a target task document, and the method further includes: If the client's acceptance conclusion for the target task document is "not approved", a preset communication record table will be displayed on the project collaboration platform. The preset communication record table is used to facilitate communication between the client and the contractor.

8. The method according to claim 4, characterized in that, The formula for calculating the overdue rate of the target project is as follows: ， ， in, This refers to the actual number of days worked by Party B. The total number of days planned for the project. The actual working time of Party B. This refers to the total working time of Party B. This is an extension of the employee's working hours. The time during which Party A inspects and provides materials during Party B's working hours.

9. The method according to claim 8, characterized in that, The method further includes: If the overdue rate of the target project is greater than or equal to the first preset threshold, and the overdue rate of the target project is less than the second preset threshold, then a deduction operation will be performed on the target project. If the overdue rate of the target project is greater than or equal to the second preset threshold, and the overdue rate of the target project is less than the third preset threshold, then the project termination option on the project collaboration platform is activated. If the overdue rate of the target project is greater than or equal to the third preset threshold, then the full amount of the target project will be deducted and the target project will be terminated.

10. The method according to claim 1, characterized in that, Each task document's conclusion for Party B corresponds to a Party B conclusion control. The formula for calculating the document pass rate is as follows: in, The number of controls that are deemed qualified by Party B in the conclusion. This represents the total number of conclusion controls for Party B.

Images