Unified project supervision service platform and project data auditing processing method

Abstract

The invention provides a project unified supervision service platform and a project data auditing processing method, and belongs to the technical field of project management. Acquiring data deviation conditions between the engineering party and other engineering parties on different priority verification project data, and determining that the engineering party does not belong to the data abnormal engineering party in combination with the data deviation conditions between the other engineering parties on different priority verification project data; performing exclusion processing on the verification project file of the data exception project party, determining an exception project file according to a deviation condition between verification project data of the verification project file of the project party which does not belong to the data exception project party, and performing return processing on the exception project file and the verification project file of the data exception project party. And the reliability of project management is improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of project management, and in particular relates to a unified project supervision service platform and a project data review and processing method. Background Art

[0002] Power construction projects require a large number of documents to be uploaded and reviewed at different project nodes. Existing technical solutions are often implemented in paper form, and late signing and document falsification often occur. At the same time, the large amount of data in project files also makes the review and processing of project file data difficult.

[0003] In response to the above technical problems, the present invention builds a unified file management and review platform to monitor and analyze the file data of different project nodes in real time, and specifically identify files with abnormalities or delayed submission, thereby improving the reliability of project supervision. Specifically, this application provides a unified project supervision service platform and a project data review and processing method. Summary of the invention

[0004] To achieve the purpose of the present invention, the present invention adopts the following technical solutions: In order to solve the above technical problems, the present invention provides the following technical solutions to achieve the purpose of the present invention: According to one aspect of the present invention, a project data review processing method is provided.

[0005] A project data review processing method, specifically comprising: S1 determines the verification project data at the current project node and the verification project files associated with the verification project data by using the project type, and determines the priority verification project data in the verification project data by the engineering parties corresponding to the verification project files associated with different verification project data; S2 determines the deviation of the verification project files of different engineering parties on the different priority verification project data, and when it is determined based on the deviation of the different priority verification project data that the engineering party does not belong to the data abnormal engineering party, proceeds to the next step; S3: obtaining the data deviation between the engineering party and other engineering parties on different priority verification item data, and when it is determined that the engineering party does not belong to the data abnormal engineering party in combination with the data deviation between other engineering parties on different priority verification item data, proceeding to the next step; S4 excludes the verification project files of the data abnormality engineering party, determines the abnormal project files according to the deviation between the verification project data of the verification project files of the engineering party that does not belong to the data abnormality engineering party, and returns the abnormal project files and the verification project files of the data abnormality engineering party.

[0006] The beneficial effects of the present invention are: 1. The priority verification project data in the verification project data are determined by the engineering parties corresponding to the verification project files associated with different verification project data, thereby realizing the determination of the priority verification project data based on the number of verification project files involved in the verification project data and the number of engineering parties involved, ensuring that the engineering parties with abnormal verification project data can be reliably identified on the priority verification project data, and also improving the efficiency of identifying and processing the engineering parties with abnormal verification project data.

[0007] 2. Abnormal project files are determined based on the deviation between the verification project data of the verification project files of the engineering party that does not belong to the engineering party with data abnormalities. This not only eliminates the abnormal interference of the verification project data of the engineering party with data abnormalities, but also improves the recognition accuracy of abnormal project files. At the same time, through the identification of abnormal project files, the reliability of engineering data management is also guaranteed.

[0008] A further technical solution is that the verification project data includes installation engineering nodes of different power equipment, test data of the power equipment and joint debugging data.

[0009] A further technical solution is that the verification project file associated with the verification project data is determined based on the verification project file in which the verification project data exists.

[0010] A further technical solution is that the method for determining the priority verification item data is: Acquire a verification project file associated with the verification project data and use it as an associated project file, determine the number of engineering parties involved in the associated project file by the engineering party corresponding to the associated project file, and determine the engineering party verification reliability coefficient of the associated project file by using the proportion of the number of engineering parties involved in the associated project file; Determine the number of associated project files of different engineering parties, and use the number of associated project files of different engineering parties to determine the verification reliability coefficients of different engineering parties; The comprehensive verification reliability coefficient of the verification item data is determined by the verification reliability coefficients of different engineering parties and the verification reliability coefficient of the engineering party, and the priority verification item data is determined by using the comprehensive verification reliability coefficient.

[0011] A further technical solution is to use the comprehensive verification reliability coefficient to determine the priority verification item data, specifically including: Based on the number of priority verification project data, the priority verification project data are determined from large to small using the comprehensive verification reliability coefficient.

[0012] A further technical solution is that the quantity of the priority verification project data is determined according to the quantity of project files of different engineering parties.

[0013] A further technical solution is to determine the data credibility values ​​of different verification item data by using different screening files based on the data deviation between the verification item data, specifically including: The number of screening files with data deviations within a preset range is determined based on the data deviations of different screening files among the verification item data, and the data credibility value of the verification item data is determined based on the proportion of the number of screening files with data deviations within the preset range.

[0014] A further technical solution is to determine the data deviation value of the screening file in different verification item data based on the deviation between the screening file and other screening files, specifically including: Based on the deviation between other screening files, other screening files whose data deviation is not within the preset range are determined, and the data deviation value of the screening file in the verification project data is determined by the proportion of the number of other screening files whose data deviation is not within the preset range.

[0015] In a second aspect, the present invention provides a unified project supervision service platform, which adopts the above-mentioned project data review and processing method, specifically comprising: Project data division module, self-deviation verification module, cross-verification module, and abnormality verification module; The project data division module is responsible for determining the verification project data at the current project node and the verification project files associated with the verification project data by using the project type, and determining the priority verification project data in the verification project data by the engineering parties corresponding to the verification project files associated with different verification project data; The self-deviation verification module is responsible for determining the deviation of verification project files of different engineering parties on different priority verification project data, and determining whether the engineering party belongs to the data abnormal engineering party based on the deviation of the different priority verification project data; The cross-check module is responsible for obtaining the data deviation between the engineering party and other engineering parties on different priority check item data, and determining whether the engineering party belongs to the data abnormal engineering party in combination with the data deviation between other engineering parties on different priority check item data; The exception verification module is responsible for excluding the verification project files of the data abnormality engineering party, determining the abnormal project files based on the deviation between the verification project data of the verification project files of the engineering party that does not belong to the data abnormality engineering party, and returning the abnormal project files and the verification project files of the data abnormality engineering party.

[0016] Other features and advantages will be described in the following description, and partly become apparent from the description, or understood by practicing the invention. The purpose and other advantages of the invention are realized and obtained by the structures particularly pointed out in the description and the drawings.

[0017] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0019] Figure 1 It is a flow chart of a project data review processing method; Figure 2 is a flow chart of a method for determining a priority verification project data; Figure 3 It is a flowchart of a method for determining abnormal project files. DETAILED DESCRIPTION

[0020] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that the present invention will be comprehensive and complete and fully convey the concepts of the example embodiments to those skilled in the art. The same reference numerals in the figures represent the same or similar structures, and thus their detailed description will be omitted.

[0021] The terms "a", "an", "the", and "said" are used to indicate the presence of one or more elements / components / etc.; the terms "comprising" and "having" are used to express an open-ended inclusive meaning and mean that additional elements / components / etc. may be present in addition to the listed elements / components / etc.

[0022] Example 1 To solve the above problems, according to one aspect of the present invention, Figure 1 According to one aspect of the present invention, a project data review processing method is provided, which specifically includes: S1 determines the verification project data at the current project node and the verification project files associated with the verification project data by using the project type, and determines the priority verification project data in the verification project data by the engineering parties corresponding to the verification project files associated with different verification project data; S2 determines the deviation of the verification project files of different engineering parties on the different priority verification project data, and when it is determined based on the deviation of the different priority verification project data that the engineering party does not belong to the data abnormal engineering party, proceeds to the next step; S3: obtaining the data deviation between the engineering party and other engineering parties on different priority verification item data, and when it is determined that the engineering party does not belong to the data abnormal engineering party in combination with the data deviation between other engineering parties on different priority verification item data, proceeding to the next step; S4 excludes the verification project files of the data abnormality engineering party, determines the abnormal project files according to the deviation between the verification project data of the verification project files of the engineering party that does not belong to the data abnormality engineering party, and returns the abnormal project files and the verification project files of the data abnormality engineering party.

[0023] Furthermore, the verification project data includes installation engineering nodes of different power equipment, test data of the power equipment and joint debugging data.

[0024] Specifically, the verification item file associated with the verification item data is determined according to the verification item file in which the verification item data exists.

[0025] Further, such as Figure 2 As shown, the method for determining the priority verification item data is: Acquire a verification project file associated with the verification project data and use it as an associated project file, determine the number of engineering parties involved in the associated project file by the engineering party corresponding to the associated project file, and determine the engineering party verification reliability coefficient of the associated project file by using the proportion of the number of engineering parties involved in the associated project file; Determine the number of associated project files of different engineering parties, and use the number of associated project files of different engineering parties to determine the verification reliability coefficients of different engineering parties; The comprehensive verification reliability coefficient of the verification item data is determined by the verification reliability coefficients of different engineering parties and the verification reliability coefficient of the engineering party, and the priority verification item data is determined by using the comprehensive verification reliability coefficient.

[0026] It should also be noted that the determination of the priority verification item data using the comprehensive verification reliability coefficient specifically includes: Based on the number of priority verification project data, the priority verification project data are determined from large to small using the comprehensive verification reliability coefficient.

[0027] Furthermore, the quantity of the priority verified project data is determined according to the quantity of project files of different engineering parties.

[0028] It should also be noted that the method for determining the priority verification item data is: S11 obtains the verification project file associated with the verification project data and uses it as the associated project file; Optionally, the above step S11 includes the following contents: Obtain the verification project file associated with the verification project data and use it as the associated project file, determine whether the number of the associated project files is less than the preset file number, if so, determine that the verification project data does not belong to the priority verification project data, if not, enter step S12.

[0029] S12: determining the number of engineering parties involved in the associated project file based on the engineering party corresponding to the associated project file, and determining the engineering party verification reliability coefficient of the associated project file based on the proportion of the number of engineering parties involved in the associated project file; Optionally, the above step S12 includes the following contents: S121: determining the number of engineering parties involved in the associated project file by the engineering party corresponding to the associated project file, determining the engineering party verification reliability coefficient of the associated project file by using the number ratio of the engineering parties involved in the associated project file, and judging whether the engineering party verification reliability coefficient of the associated project file meets the requirement, if yes, proceeding to the next step, if no, proceeding to step S13; S122 determines the number of associated project files of different engineering parties, and judges whether the number of engineering parties whose number of associated project files is greater than a preset number threshold meets the requirement. If so, it is determined that the verification project data does not belong to the priority verification project data. If not, enter step S13.

[0030] S13 determines the number of associated project files of different engineering parties, and uses the number of associated project files of different engineering parties to determine the verification reliability coefficients of different engineering parties, determines the comprehensive verification reliability coefficient of the verification project data with the verification reliability coefficients of different engineering parties and the engineering party verification reliability coefficient, and uses the comprehensive verification reliability coefficient to determine the priority verification project data.

[0031] Optionally, the above step S13 includes the following contents: S131 determines the number of associated project files of different engineering parties, and uses the number of associated project files of different engineering parties to determine the verification reliability coefficients of different engineering parties, and determines whether the number of engineering parties whose verification reliability coefficients meet the requirements is greater than the preset number of engineering parties. If so, it is determined that the verification project data does not belong to the priority verification project data. If not, proceed to step S132; S132 determines the comprehensive verification reliability coefficient of the verification item data by using the verification reliability coefficients of different engineering parties and the verification reliability coefficient of the engineering party, and uses the comprehensive verification reliability coefficient to determine the priority verification item data.

[0032] Furthermore, the deviation situation on the priority verification item data includes the data deviation amount between the verification item files associated with different verification item data.

[0033] It can be understood that determining that the engineering party does not belong to the data abnormal engineering party based on the deviation of different priority verification item data specifically includes: The verification project files associated with the priority verification project data are used as priority associated files, and the data reliability coefficients of the engineering party on different priority verification project data are determined by the data deviations between the priority associated files of the engineering party on the priority verification project data, and the comprehensive data reliability coefficient of the engineering party is determined by the data reliability coefficients on different priority project data; Determine the reliability of file data of different priority associated files by using the data deviation between the priority associated file and other priority associated files on different priority inspection item data, and determine the file reliability coefficient of the engineering party by using the file data reliability of different priority associated files; The engineering data reliability coefficient of the engineering party is determined based on the average value of the comprehensive data reliability coefficient and the file reliability coefficient, and the engineering data reliability coefficient is used to determine whether the engineering party is a data abnormal engineering party.

[0034] Furthermore, when the engineering data reliability coefficient of the engineering party does not meet the requirements, the engineering party is determined to be a data abnormal engineering party.

[0035] It should be noted that, when the engineering party is a data abnormality engineering party, the verification project file of the data abnormality engineering party is directly returned for processing.

[0036] It should also be noted that the determination that the engineering party does not belong to the data abnormal engineering party based on the deviation of the data of different priority verification items specifically includes: S21: taking the verification project file associated with the priority verification project data as the priority associated file, and determining the data reliability coefficient of the engineering party on different priority verification project data by respectively using the data deviation between the priority associated files of the engineering party on the priority verification project data; Optionally, the above step S21 includes the following contents: S211: taking the verification project file associated with the priority verification project data as the priority associated file, determining the data reliability coefficient of the engineering party on different priority verification project data through the data deviation between the priority associated files of the engineering party on the priority verification project data, and judging whether there is priority verification project data whose data reliability coefficient does not meet the requirements, if yes, proceeding to the next step, if no, proceeding to step S22; S212 determines whether the proportion of the number of priority verification project data whose data reliability coefficient does not meet the requirement meets the requirement, if so, proceeds to the next step, if not, determines that the engineering party belongs to the data abnormal engineering party; S213 determines the comprehensive data reliability coefficient of the engineering party based on the data reliability coefficients of different priority project data, and judges whether the comprehensive data reliability coefficient of the engineering party meets the requirements. If so, enters step S22; if not, it is determined that the engineering party belongs to the data abnormal engineering party.

[0037] S22 determines the reliability of file data of different priority associated files by using the data deviation between the priority associated file and other priority associated files on different priority inspection item data; Optionally, the above step S22 includes the following contents: S22 utilizes the data deviation between the priority associated file and other priority associated files on different priority inspection item data to determine the file data reliability of different priority associated files, and judges whether there are priority associated files whose file data reliability does not meet the requirements. If so, proceed to step S23; if not, determine that the engineering party does not belong to the data abnormality engineering party.

[0038] S23 determines the file reliability coefficient of the engineering party through the file data reliability of different priority associated files, determines the engineering data reliability coefficient of the engineering party based on the comprehensive data reliability coefficient and the average value of the file reliability coefficient, and uses the engineering data reliability coefficient to determine whether the engineering party is a data abnormal engineering party.

[0039] Optionally, the above step S23 includes the following contents: S231 determines the file reliability coefficient of the engineering party through the file data reliability of different priority associated files, and judges whether the file reliability coefficient of the engineering party meets the requirements. If so, it is determined that the engineering party does not belong to the data abnormal engineering party. If not, proceed to the next step; S232 determines the engineering data reliability coefficient of the engineering party based on the average value of the comprehensive data reliability coefficient and the file reliability coefficient, and uses the engineering data reliability coefficient to determine whether the engineering party is a data abnormal engineering party.

[0040] Further, combining the data deviations between other engineering parties on different priority verification item data to determine that the engineering party does not belong to the engineering party with abnormal data, specifically includes: Based on the data deviation conditions of the other engineering parties on the different priority verification project data, the data deviation amounts of the other engineering parties on the different priority verification project data are calculated, and based on the data deviation amounts of the other engineering parties on the different priority verification project data, the data credibility coefficients of the different priority verification project data are determined; Determining the data deviation coefficient of the engineering party on the data of different priority verification items based on the data deviation between the engineering party and other engineering parties on the data of different priority verification items; The comparison reliability coefficient of the engineering party is determined by using the data deviation coefficient and data credibility coefficient of different priority verification project data, and the comparison reliability coefficient is used to determine whether the engineering party is a data abnormal engineering party.

[0041] It should be noted that when the comparison reliability coefficient of the engineering party is not within a preset interval, it is determined that the engineering party is a data abnormal engineering party.

[0042] Furthermore, when the engineering party is a data abnormality engineering party, the verification project file of the data abnormality engineering party is directly returned for processing.

[0043] It should also be noted that the engineering party is determined not to be a data abnormal engineering party in combination with the data deviations of other engineering parties on different priority verification project data, specifically including: S31, based on the data deviation between the engineering party and other engineering parties on different priority verification item data, determining the data deviation coefficient of the engineering party on different priority verification item data; S32: taking the priority verification project data whose data deviation coefficient does not meet the requirements as deviation project data, performing data deviation amounts on different priority verification project data between different other engineering parties based on data deviation conditions on different priority verification project data between other engineering parties, and determining data credibility coefficients of different priority verification project data based on data deviation amounts on different priority verification project data between different other engineering parties; S33 determines the comparison reliability coefficient of the engineering party through the data deviation amount and data credibility coefficient of different priority verification project data, and uses the comparison reliability coefficient to determine whether the engineering party belongs to the data abnormal engineering party.

[0044] Specifically, Figure 3 As shown, the method for determining the abnormal project file is: Determine the abnormal project file based on the deviation between the verification project data of the verification project file of the engineering party that does not belong to the data abnormal engineering party Using the verification project file of the engineering party that does not belong to the data abnormal engineering party as a screening file, and determining the deviation between different verification project data of the screening file and other screening files; Determine the data deviation value of the screening file in different verification item data based on the deviation between the screening files and other screening files, and determine the data credibility value of different verification item data by using the data deviation between the verification item data of different screening files; The data anomaly assessment amount of the screening file is determined by the sum of the products of the data deviation value and the data credibility value of different verification item data, and whether the screening file is an abnormal item file is determined by the data anomaly assessment amount.

[0045] Further, when the data anomaly assessment amount of the screening file is greater than a preset anomaly threshold, the screening file is determined to be an abnormal project file.

[0046] It should also be noted that the data credibility values ​​of different verification item data are determined by using different screening files according to the data deviation between the verification item data, specifically including: The number of screening files with data deviations within a preset range is determined based on the data deviations of different screening files among the verification item data, and the data credibility value of the verification item data is determined based on the proportion of the number of screening files with data deviations within the preset range.

[0047] It can be understood that determining the data deviation value of the screening file in different verification item data based on the deviation between the screening file and other screening files specifically includes: Based on the deviation between other screening files, other screening files whose data deviation is not within the preset range are determined, and the data deviation value of the screening file in the verification project data is determined by the proportion of the number of other screening files whose data deviation is not within the preset range.

[0048] Optionally, the above step S31 includes the following contents: Based on the data deviation between the engineering party and other engineering parties on different priority verification project data, the data deviation coefficient of the engineering party on different priority verification project data is determined, and it is judged whether there is priority verification project data whose data deviation coefficient does not meet the requirements. If so, proceed to step S32, if not, determine that the engineering party does not belong to the data abnormal engineering party.

[0049] Optionally, the above step S32 includes the following contents: S321: taking the priority verification item data whose data deviation coefficient does not meet the requirements as the deviation item data, and judging whether the quantity of the deviation item data is within the preset quantity range, if yes, proceeding to the next step, if no, proceeding to step S33; S322: based on the data deviation conditions of the other engineering parties on the different priority verification project data, the data deviation amounts of the other engineering parties on the different priority verification project data are determined, and based on the data deviation amounts of the other engineering parties on the different priority verification project data, the data credibility coefficients of the different priority verification project data are determined, and whether the number of deviation project data whose data credibility coefficients meet the requirements is determined, if so, proceeding to the next step, if not, determining that the engineering party belongs to the data abnormal engineering party; S323 determines the comprehensive deviation coefficient of different deviation project data by the product of the data deviation coefficient and the data credibility coefficient of different deviation project data, and judges whether the number of deviation project data whose comprehensive deviation coefficient does not meet the requirements meets the requirements. If so, enters step S33, if not, it determines that the engineering party belongs to the data abnormality engineering party.

[0050] Example 2 In a second aspect, the present invention provides a unified project supervision service platform, which adopts the above-mentioned project data review and processing method, specifically comprising: Project data division module, self-deviation verification module, cross-verification module, and abnormality verification module; The project data division module is responsible for determining the verification project data at the current project node and the verification project files associated with the verification project data by using the project type, and determining the priority verification project data in the verification project data by the engineering parties corresponding to the verification project files associated with different verification project data; The self-deviation verification module is responsible for determining the deviation of verification project files of different engineering parties on different priority verification project data, and determining whether the engineering party belongs to the data abnormal engineering party based on the deviation of the different priority verification project data; The cross-check module is responsible for obtaining the data deviation between the engineering party and other engineering parties on different priority check item data, and determining whether the engineering party belongs to the data abnormal engineering party in combination with the data deviation between other engineering parties on different priority check item data; The exception verification module is responsible for excluding the verification project files of the data abnormality engineering party, determining the abnormal project files based on the deviation between the verification project data of the verification project files of the engineering party that does not belong to the data abnormality engineering party, and returning the abnormal project files and the verification project files of the data abnormality engineering party.

[0051] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0052] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0053] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A project data review processing method, characterized in that: Specifically include: Determine the verification project data at the current project node and the verification project files associated with the verification project data by using the project type, and determine the priority verification project data in the verification project data by using the engineering parties corresponding to the verification project files associated with different verification project data; Determine the deviation of the verification project files of different engineering parties on the different priority verification project data, and when it is determined based on the deviation on the different priority verification project data that the engineering party does not belong to the data abnormal engineering party, proceed to the next step; Obtain the data deviation between the engineering party and other engineering parties on different priority verification project data, and when it is determined that the engineering party does not belong to the data abnormal engineering party in combination with the data deviation between other engineering parties on different priority verification project data, proceed to the next step; The verification project files of the data abnormality engineering party are excluded, and the abnormal project files are determined based on the deviation between the verification project data of the verification project files of the engineering party that does not belong to the data abnormality engineering party, and the abnormal project files and the verification project files of the data abnormality engineering party are returned.

2. The project data review processing method according to claim 1, characterized in that: The verification project data includes installation engineering nodes of different power equipment, test data of power equipment and joint debugging data.

3. The project data review processing method according to claim 1, characterized in that: The verification item file associated with the verification item data is determined based on the verification item file in which the verification item data exists.

4. The project data review processing method according to claim 1, characterized in that: The method for determining the priority verification item data is: Acquire a verification project file associated with the verification project data and use it as an associated project file, determine the number of engineering parties involved in the associated project file by the engineering party corresponding to the associated project file, and determine the engineering party verification reliability coefficient of the associated project file by using the proportion of the number of engineering parties involved in the associated project file; Determine the number of associated project files of different engineering parties, and use the number of associated project files of different engineering parties to determine the verification reliability coefficients of different engineering parties; The comprehensive verification reliability coefficient of the verification item data is determined by the verification reliability coefficients of different engineering parties and the verification reliability coefficient of the engineering party, and the priority verification item data is determined by using the comprehensive verification reliability coefficient.

5. The project data review processing method according to claim 4, characterized in that: Determining the priority verification item data by using the comprehensive verification reliability coefficient specifically includes: Based on the number of priority verification project data, the priority verification project data are determined from large to small using the comprehensive verification reliability coefficient.

6. The project data review processing method according to claim 1, characterized in that: The deviation situation of the priority verification item data includes the data deviation amount between the verification item files associated with different verification item data.

7. The project data review processing method according to claim 1, characterized in that: Determining that the engineering party does not belong to the data abnormal engineering party based on the deviation of the data of different priority verification items includes: The verification project files associated with the priority verification project data are used as priority associated files, and the data reliability coefficients of the engineering party on different priority verification project data are determined by the data deviations between the priority associated files of the engineering party on the priority verification project data, and the comprehensive data reliability coefficient of the engineering party is determined by the data reliability coefficients on different priority project data; Determine the reliability of file data of different priority associated files by using the data deviation between the priority associated file and other priority associated files on different priority inspection item data, and determine the file reliability coefficient of the engineering party by using the file data reliability of different priority associated files; The engineering data reliability coefficient of the engineering party is determined based on the average value of the comprehensive data reliability coefficient and the file reliability coefficient, and the engineering data reliability coefficient is used to determine whether the engineering party is a data abnormal engineering party.

8. The project data review processing method according to claim 7, characterized in that: When the engineering data reliability coefficient of the engineering party does not meet the requirements, the engineering party is determined to be a data abnormal engineering party.

9. A unified project supervision service platform, using a project data review and processing method according to any one of claims 1 to 8, characterized in that: Specifically include: Project data division module, self-deviation verification module, cross-verification module, and abnormality verification module; The project data division module is responsible for determining the verification project data at the current project node and the verification project files associated with the verification project data by using the project type, and determining the priority verification project data in the verification project data by the engineering parties corresponding to the verification project files associated with different verification project data; The self-deviation verification module is responsible for determining the deviation of verification project files of different engineering parties on different priority verification project data, and determining whether the engineering party belongs to the data abnormal engineering party based on the deviation of the different priority verification project data; The cross-check module is responsible for obtaining the data deviation between the engineering party and other engineering parties on different priority check item data, and determining whether the engineering party belongs to the data abnormal engineering party in combination with the data deviation between other engineering parties on different priority check item data; The exception verification module is responsible for excluding the verification project files of the data abnormality engineering party, determining the abnormal project files according to the deviation between the verification project data of the verification project files of the engineering party that does not belong to the data abnormality engineering party, and returning the abnormal project files and the verification project files of the data abnormality engineering party.

Images