Engineering project multi-source management platform

Abstract

The invention relates to the technical field of engineering project management, in particular to an engineering project multi-source management platform, which comprises a data acquisition module, a data analysis module, a data processing module and a data processing module, the project permission type determining module is used for calculating a project permission type tendency value based on the first complexity and the second complexity, and determining a project permission type based on a comparison result of the project permission type tendency value and a preset project permission type tendency value; the permission extension module is used for differentially extending project permissions when determining that the project has conflict data based on the project permission type and / or the sensitivity degree of the project conflict data; the authority recycling module is used for determining whether to recycle the extension authority or not based on whether the project stage is changed or not and / or whether the authority extension user meets the negative access condition or not, and multi-source engineering project management is achieved by improving the accuracy of authority dynamic management when conflict data occurs.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of engineering project management, and particularly relates to a multi-source management platform for engineering projects. BACKGROUND

[0002] Engineering project management is a complex process involving multiple stages, multiple participants, and a large amount of data interaction. Traditional engineering project management usually relies on manual coordination and paper documents, which is inefficient and prone to problems such as inconsistent information and poor communication. Although existing engineering project management platforms already have some data management functions, there are still the following problems: scattered data sources: project data may come from multiple different systems or departments, lacking unified integration and management, leading to inconsistent data and information silos; complex permission management: in a multi-user, multi-stage engineering project, permission management is a key issue. Existing platforms usually use static permission settings, which cannot dynamically adjust permissions according to changes in project stages or the occurrence of conflicting data; insufficient conflict data processing: data conflicts are inevitable in engineering projects, such as inconsistent modification opinions on the same data by different stages or different users. Existing platforms have limited capabilities for processing conflicting data, lacking effective sensitivity assessment and dynamic permission adjustment mechanisms.

[0003] For example, Chinese patent application publication No. CN113240403A discloses an engineering construction project management system and method based on multi-source data, which includes extracting multi-source data related to engineering construction projects from local databases and external data sources, obtaining project status monitoring data in a multi-source database to construct a BIM model; calling and managing each item of business data involved in the BIM model; reading BIM model information and rendering and displaying corresponding three-dimensional visual BIM model images on the display interface; finally, assigning task objectives and task association information to each project team according to its jurisdiction, and displaying personalized functions, pushing to-do items, feeding back task-related data, and statistical analysis reports to different user objects in the form of three-dimensional visual BIM model images. The above scheme combines data indexing technology and three-dimensional visualization technology to achieve fast BIM modeling and lightweight presentation; through the data access bus and processing center, the heterogeneous data is connected, solving the problems of multi-source data storage, processing, and presentation.

[0004] However, the prior art has the problem that when project conflict data occurs, it cannot accurately and dynamically allocate project permissions, resulting in project conflict data not being solved in a timely manner, causing low efficiency and low precision in engineering project management. SUMMARY

[0005] To this end, the application provides an engineering project multi-source management platform to overcome the problem of low project management efficiency and low management accuracy caused by the inability to accurately and dynamically allocate project permissions when project conflict data occurs in the prior art.

[0006] To achieve the above-mentioned purpose, the application provides an engineering project multi-source management platform, comprising:

[0007] A data acquisition module is configured to acquire project content information, project implementation process information, and project data source information, and match the project information with an industry standard stage template to obtain project division stage information and associated user information of each stage.

[0008] A data analysis module is connected to the data acquisition module and comprises,

[0009] A first calculation unit is configured to calculate a first complexity degree based on the number of project division stages and the deviation degree of the number of edges of the implementation route topology graph from the number of edges of a complete graph.

[0010] A second calculation unit is configured to calculate a second complexity degree based on the number of associated users of each stage and the difference degree of the permission levels of the associated users of each stage.

[0011] A project permission type analysis unit is connected to the first calculation unit and the second calculation unit, respectively, and is configured to calculate a project permission type tendency value based on the first complexity degree and the second complexity degree, and determine the project permission type based on the comparison result of the project permission type tendency value and a preset project permission type tendency value.

[0012] A permission extension module is connected to the data analysis module and is configured to determine the differentiated extension of project permissions when there is project conflict data based on the sensitivity of the project permission type and / or the project conflict data.

[0013] A permission recovery module is connected to the permission extension module and is configured to determine whether to recover the extended permissions based on whether the project stage has changed and / or whether the permission extension user meets the negative access condition.

[0014] A monitoring module is connected to the permission recovery module and is configured to determine whether to mark the multiple-time permission extension user or monitor the change amount of project conflict data after the extension permissions are recovered based on whether there is a multiple-time permission extension user when the extended permissions are recovered.

[0015] Further, the first calculation unit calculates the first complexity degree based on the ratio of the number of project division stages to a preset number and the deviation degree of the number of edges of the implementation route topology graph from the number of edges of a complete graph.

[0016] Further, the second calculation unit calculates the second complexity degree based on a ratio of the number of associated users of each stage to a preset number of associated users and a ratio of a difference degree of the permission level of the associated users of each stage to a preset difference degree.

[0017] Further, the project permission type analysis unit calculates a project permission type tendency value based on a product of the first complexity degree and a weight coefficient thereof and a product of the second complexity degree and a weight coefficient thereof.

[0018] Further, the project permission type analysis unit determines the project permission type based on a comparison result of the project permission type tendency value and a preset project permission type tendency value, wherein,

[0019] If the project permission type tendency value is greater than or equal to the preset project permission type tendency value, the project permission type analysis unit determines that the project permission type is a project permission complex type.

[0020] If the project permission type tendency value is less than the preset project permission type tendency value, the project permission type analysis unit determines that the project permission type is a project permission simple type.

[0021] Further, the permission extension module determines a differentiated extension project permission when the project exists in conflict data based on the project permission type and / or a sensitive degree of the project conflict data, wherein,

[0022] If the project permission type is a permission simple type and the sensitive degree of the project conflict data is less than a preset sensitive degree, the permission extension module determines a non-differentiated extension project permission.

[0023] If the project permission type is a permission complex type or the sensitive degree of the project conflict data is greater than or equal to the preset sensitive degree, the permission extension module determines a differentiated extension project permission.

[0024] Further, the sensitive degree of the project conflict data is determined according to a number of associated stages of the project conflict data.

[0025] Further, the permission recovery module determines whether to recover the extended permission based on whether the project stage has changed and / or whether the permission extension user satisfies a negative access condition, wherein,

[0026] If the project stage has changed or the permission extension user satisfies the negative access condition, the permission recovery module determines to recover the extended permission.

[0027] If the project stage has not changed and the permission extension user does not satisfy the negative access condition, the permission recovery module determines not to recover the extended permission.

[0028] The negative access condition is that a user access interval is greater than a preset access interval.

[0029] Further, the monitoring module is configured to determine whether to mark the multi-time permission extension user or monitor the change trend of the project conflict data after the extension permission is recycled based on whether there is a multi-time permission extension user when the extension permission is recycled,

[0030] If there is a multi-time permission extension user, it is determined to mark the multi-time permission extension user.

[0031] If there is no multi-time permission extension user, it is determined to monitor the change trend of the project conflict data after the extension permission is recycled.

[0032] Further, the monitoring module is configured to determine whether to perform secondary permission extension based on the change trend of the project conflict data after the extension permission is recycled, wherein,

[0033] If the change trend of the project conflict data after the extension permission is recycled is a non-decreasing trend, the monitoring module determines to perform secondary permission extension.

[0034] Compared with the prior art, the present application has the beneficial effects that the present application realizes multi-dimensional quantitative analysis, improves the precision of permission management, the first complexity reflects the complexity of the project implementation path, the more stages and the more complex the dependency relationship, the higher the requirement for fine-grained control of permissions; the second complexity evaluates the management difficulty on the user side, the more users and the greater the permission difference, the risk of permission conflict grows exponentially; through double-dimensional quantification, the evaluation deviation caused by a single indicator is avoided, and the core challenge of permission management is more comprehensively captured; the weight coefficient is updated with historical data iteration, adapting to the changes in project management trends; compared with fixed weight, the weight of the model training is more objective, reducing subjective errors; by comparing the project permission type tendency value with the preset threshold, the permission type is automatically determined to be "simple" or "complex", avoiding the subjectivity and time-consuming of manual evaluation; quickly matching the permission management strategy: for example, the multi-role approval process and fine-grained permission control (such as data access isolation by stage) are automatically triggered for complex type projects; the standardized permission template is used for simple type projects to improve efficiency; and the over-configuration (such as setting complex permission levels for simple projects) or under-configuration (such as too coarse permission granularity for complex projects) of permissions caused by insufficient experience of managers is avoided.

[0035] Further, the application realizes precise permission control based on risk grading, and the permission type and the conflict data sensitivity degree jointly determine the extension strategy; single permission management is avoided, security and collaboration efficiency are balanced, users directly operating (such as the creator of the design change order and the modifier of the construction log) are extracted from the creation, modification and approval record of the conflict data, and the highest permission is preferentially given; for example, when the construction record and the design drawing conflict in material consumption, the directly associated user (the execution layer) can immediately obtain the correction permission, and the problem processing cycle is shortened; the non-key user (the monitoring layer) only obtains the basic access permission, and irrelevant personnel are prevented from interfering with the conflict solution; non-differentiated extension (synchronous permission for all personnel) is applicable to low-risk scenarios, and the permission configuration workload is reduced; under the differentiated extension of complex type projects or high sensitivity conflicts, only necessary users are given high permission, and system resource consumption is reduced.

[0036] Further, the application realizes precise recovery based on stage changes and access behaviors, when the project enters the development stage from the design stage, the extension permission of the design stage (such as the modification permission of the design drawing) is automatically recovered; when the project stage is iterated, the permission of the old stage is automatically recovered, ensuring that the permission strictly matches the current work content, automatically recovering unnecessary permissions, reducing permission audit and maintenance costs, recovering idle permissions can reduce the number of permission records stored by the system, and optimizing the permission verification efficiency; the differentiated extension permission is accurately recovered when the stage is changed or the user is idle, forming a closed loop.

[0037] Further, the application accurately identifies permission design defects and optimizes the permission system, through audit history extension records, the system can identify high-frequency requirements (such as an engineer frequently needing to access test environment data), and convert them into regular permission configurations, reducing temporary approval processes; the system automatically reviews the permission use records of multiple users, and identifies abnormal operations; temporary permissions are automatically recovered and cannot be renewed (such as needing to reapply if continued use is required); reducing repeated approval overhead, saving approval time and labor costs after converting high-frequency extension permissions into regular permissions; reducing dynamic allocation of temporary permissions and reducing the computational complexity of permission verification.

[0038] Further, the application automatically determines whether secondary extension is needed by monitoring the trend of conflict data volume changes, avoids the lag of manual intervention, needs secondary extension to the quality inspector when the trend is not decreasing (such as the conflict data volume being flat or increasing after the permission is recovered), ensures process closure, maintains the status quo when the trend is decreasing, and avoids over-authorization; secondary permission extension to the quality inspector solves common process bottlenecks; secondary extension is only performed when the conflict data is not decreasing, preventing permission abuse; process closure problems are solved through secondary permission extension, and conflicts are reduced from the source. BRIEF DESCRIPTION OF DRAWINGS

[0039] Figure 1The structural schematic diagram of the project multi-source management platform of the embodiment of the present application is shown in the figure;

[0040] Figure 2 The structural schematic diagram of the data analysis module in the project multi-source management platform of the embodiment of the present application is shown in the figure;

[0041] Figure 3 The working flow chart of the data analysis module in the project multi-source management platform of the embodiment of the present application is shown in the figure;

[0042] Figure 4 The working flow chart of the permission extension module in the project multi-source management platform of the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0043] In order to make the objects and advantages of the present application clearer, the present application will be further described below in conjunction with embodiments; it should be understood that the specific embodiments described herein are only used to explain the present application and not to limit the present application.

[0044] The preferred embodiments of the present application will be described below with reference to the accompanying drawings. It should be understood by those skilled in the art that the embodiments are only used to explain the technical principles of the present application and not to limit the protection scope of the present application.

[0045] In addition, it should be further explained that, in the description of the present application, unless explicitly defined and limited, the terms “mounting”, “connecting”, “connection” should be understood in a broad sense, for example, it can be fixed connection, or detachable connection, or integrally connected; it can be mechanical connection, or electrical connection; it can be directly connected, or indirectly connected through an intermediate medium, or the internal communication of two elements. Those skilled in the art can understand the specific meaning of the above terms in the present application according to the specific circumstances.

[0046] Please refer to Figures 1-4 shown, Figure 1 The structural schematic diagram of the project multi-source management platform of the embodiment of the present application is shown in the figure; Figure 2 The structural schematic diagram of the data analysis module in the project multi-source management platform of the embodiment of the present application is shown in the figure; Figure 3 The working flow chart of the data analysis module in the project multi-source management platform of the embodiment of the present application is shown in the figure; Figure 4 The working flow chart of the permission extension module in the project multi-source management platform of the embodiment of the present application is shown in the figure.

[0047] The project multi-source management platform of the embodiment of the present application comprises:

[0048] a data acquisition module configured to acquire project content information, project implementation process information, and project data source information, and match the project information with an industry standard stage template to obtain project division stage information and associated user information of each stage;

[0049] a data analysis module connected to the data acquisition module and comprising,

[0050] a first calculation unit configured to calculate a first complexity degree based on a number of project division stages and a deviation degree of an edge number of an implementation route topology graph from an edge number of a complete graph;

[0051] a second calculation unit configured to calculate a second complexity degree based on a number of associated users of each stage and a difference degree of permission levels of the associated users of each stage;

[0052] a project permission type analysis unit connected to the first calculation unit and the second calculation unit respectively, configured to calculate a project permission type tendency value based on the first complexity degree and the second complexity degree, and determine the project permission type based on a comparison result of the project permission type tendency value and a preset project permission type tendency value;

[0053] a permission extension module connected to the data analysis module, configured to determine a differentiated extension of project permissions when there is project conflict data based on a project permission type and / or a sensitive degree of the project conflict data;

[0054] a permission recovery module connected to the permission extension module, configured to determine whether to recover the extended permissions based on whether a project stage has changed and / or whether a permission extension user meets a negative access condition;

[0055] a monitoring module connected to the permission recovery module, configured to determine whether to mark a multiple-time permission extension user or monitor a change amount of project conflict data after the extended permissions are recovered based on whether there is the multiple-time permission extension user when the extended permissions are recovered.

[0056] In the embodiments of the present application, the project content information includes but is not limited to “basic attribute information (such as a project BIM model and design drawings), technical scheme information (such as a construction organization design and a special construction scheme), and economic management information (such as a project budget and a cost breakdown table)”, the project implementation process information includes but is not limited to “progress management data, quality management data, and safety management data”, the project data source information includes but is not limited to “internal data sources (such as project management system (e.g., ERP, PMIS) input data) and external data sources (such as a supplier management system (material traceability data, equipment qualification certificate))”, and the permission extension user is an associated user of the project conflict data.

[0057] The data acquisition module in the embodiment of the application matches the project information with the industry standard stage template to obtain project division stage information and associated user information of each stage. For example, the data acquisition module realizes the matching of the project information and the industry standard stage template through semantic association analysis and knowledge graph mapping. For example, the matching is based on the project content information. The input data includes the project content information containing the "XX Mansion building structure BIM model". The matching process includes the following steps. The keywords are extracted, including the BIM model, the building structure, and the design. The "design stage" in the industry standard template is defined. The optional information includes the preliminary design drawing, the BIM model, and the design change record. The associated users include the project manager of the design institute, the structural engineer, and the cost consulting unit. The matching result includes the project division stage and the associated users. The project division stage is the design stage. The associated users are automatically associated with the project manager of the design institute (the permission level is design approval), the structural engineer (the permission level is design editing), and the like.

[0058] Specifically, the first calculation unit calculates the first complexity degree based on the ratio of the number of project division stages to a preset number and the deviation degree of the number of edges of the implementation route topology graph from the number of edges of a complete graph.

[0059] In the embodiment of the application, the first complexity degree is the sum of the ratio of the number of project division stages to a preset number and the deviation degree of the number of edges of the implementation route topology graph from the number of edges of a complete graph and 1. The deviation degree of the number of edges of the implementation route topology graph from the number of edges of a complete graph reflects the difference degree between the actual implementation path of the project and the most complex path (i.e., a complete graph). The higher the deviation degree is, the simpler the dependence relationship between the project stages is (the number of edges is less). The lower the deviation degree is, the more complex the relationship between the stages is (the number of edges is close to the number of edges of a complete graph). For example, each stage of the project is regarded as a node in a graph, the dependence relationship or implementation sequence between the stages is regarded as an edge, a complete graph refers to a graph in which there is an edge between any two nodes, and the deviation degree of the number of edges of the implementation route topology graph from the number of edges of a complete graph is the absolute value of the difference between 1 and the ratio of the actual number of edges of the project implementation route topology graph to the number of edges of a complete graph with the same number of nodes. The preset number is the average value of the number of stages of historical similar projects, but the above-mentioned value is not limited thereto, and a person skilled in the art can adjust the value according to actual needs.

[0060] It can be understood that the more the project stages are, the more the milestone nodes are, and the more precise the progress tracking needs to be. The more the stage connection points are, and the higher the frequency of cross-stage cooperation is. The resources need to be allocated among more stages, and resource conflicts are prone to occur. The low deviation degree (the number of edges is close to the number of edges of a complete graph): there are a large number of parallel or circular dependencies between the stages (for example, the construction preparation is started before the design stage is completed), high-frequency coordination of cross-stage tasks is needed, and process conflicts are prone to occur. The high deviation degree (the number of edges is less): the dependence relationship between the stages is clear, and the management difficulty is low.

[0061] Specifically, the second calculation unit calculates the second complexity based on the ratio of the number of associated users in each stage to the preset number of associated users and the ratio of the degree of difference in authority levels of associated users in each stage to the preset degree of difference.

[0062] In an embodiment of the present invention, the second complexity level is the sum of the ratio of the number of associated users in each stage to the preset number of associated users, and the ratio of the degree of difference in the authority levels of the associated users in each stage to the preset degree of difference. The degree of difference in the authority levels of the associated users in each stage is the average value of the degree of difference in the authority levels of the associated users in each project division stage. The degree of difference in the authority levels of the associated users in a single project division stage is determined by the ratio of the maximum number of associated users in a single authority level in a single project division stage to the number of associated users in the single project division stage. The preset number of associated users is the average value of the number of associated users in each stage in historical similar projects. The preset degree of difference is the average value of the degree of difference in the authority levels of the associated users in each stage in historical similar projects. For example, for each stage of historical similar projects, the degree of difference in the authority levels of the associated users in that stage is calculated (that is, the ratio of the maximum number of associated users in a single authority level in a single stage to the total number of associated users in that stage); the degree of difference of all stages is summarized and averaged to obtain the preset degree of difference.

[0063] It is understandable that the more users associated with a single stage, the more roles that need to be covered by permission allocation (such as adding a third-party consultant in the design stage), and the permission configuration granularity requirements are higher; when multiple users operate on data at the same time, the risk of permission conflict (such as multiple people modifying the same data at the same time) increases exponentially; a high degree of difference (such as the coexistence of a few high-privilege users and a large number of low-privilege users) is prone to abnormal phenomena such as high-privilege users making slow decisions or low-privilege users attempting to exceed their authority.

[0064] Specifically, the project authority type analysis unit calculates the project authority type tendency value based on the product of the first complexity and its weight coefficient and the product of the second complexity and its weight coefficient.

[0065] The weight coefficient of the first complexity degree and the weight coefficient of the second complexity degree in the embodiment of the application can be determined by the following method: training a model (such as a random forest or a neural network) using historical project data, taking the first complexity degree and the second complexity degree as features, and taking the permission type as a label, obtaining the optimal weight coefficient through model training, and periodically iterating the model according to new data to dynamically update the weight to adapt to the project trend changes. For example, first, historical project data is collected, including the following contents: the first complexity degree: the ratio of the number of project division stages to the preset number, and the deviation degree of the number of edges of the implementation route topology graph from the number of edges of the complete graph; the second complexity degree: the ratio of the number of associated users in each stage to the preset number of associated users, and the ratio of the permission level difference degree of the associated users in each stage to the preset difference degree; the permission type: the actual determined permission type (such as a simple type or a complex type) in the historical project; the above data is arranged into a feature vector for model training, for example: feature 1: the first complexity degree; feature 2: the second complexity degree; label: permission type (simple type or complex type); a suitable machine learning model is selected for training, common models include random forest, neural network and support vector machine; the model is trained using historical project data; the specific steps are as follows: data division: divide the historical project data into a training set and a test set, usually in a ratio of 7:3 or 8:2; model training: use the training set data to train the selected model, and adjust the parameters of the model to optimize the performance; model evaluation: use the test set data to evaluate the trained model, calculate the classification accuracy, recall rate, F1 value and other indicators to ensure that the performance of the model meets the requirements; the optimal weight coefficient obtained through model training can be extracted from the feature importance or weight parameter of the model; for example: random forest: the model outputs the importance score of each feature, which can be normalized as the weight coefficient; neural network: the input layer to the hidden layer weight can be extracted by analyzing the weight parameter of the neural network, and normalized as the weight coefficient; the model needs to be periodically updated according to new data to adapt to the changes in the project trend; the specific steps are as follows: data collection: periodically collect new project data, including the first complexity degree, the second complexity degree and the permission type; model update: retrain or incrementally update the model using new data, and adjust the weight coefficient to reflect the latest project trend; weight adjustment: extract the new weight coefficient from the updated model for project permission type analysis; the value of the weight coefficient of the first complexity degree in the embodiment of the application is preferably 0.61, and the value of the weight coefficient of the second complexity degree is preferably 0.39, but the above values are not limited thereto, and a person skilled in the art can adjust the values according to actual needs.

[0066] Specifically, the project permission type analysis unit determines the project permission type based on a comparison result of the project permission type tendency value and a preset project permission type tendency value.

[0067] If the project permission type tendency value is greater than or equal to a preset project permission type tendency value, the project permission type analysis unit determines the project permission type as a project permission complex type;

[0068] If the project permission type tendency value is less than the preset project permission type tendency value, the project permission type analysis unit determines the project permission type as a project permission simple type.

[0069] The preset project permission type tendency value in the embodiment of the application can be determined by the following method: collecting the permission type tendency values of historical projects; calculating the permission type tendency value of each historical project; manually marking it as a "simple type" or a "complex type" according to the actual management situation of the project (for example, a permission conflict frequency (referring to the average number of conflict events per month caused by permission allocation problems in the project) greater than 5 times per month is regarded as a complex type); using the ROC curve or KS test to find the best boundary point to make the classification accuracy the highest;

[0070] For example, if 80% of the projects with a tendency value greater than or equal to 0.65 in the historical data are marked as complex types, the preset value can be set to 0.65; example: historical project tendency value distribution: simple type mean = 0.45, complex type mean = 0.72; take the midpoint (such as 0.58) of the two type means as the preset project permission type tendency value; but the above value is not limited to this, and the skilled person in the art can also adjust the value according to the actual needs.

[0071] The application realizes multi-dimensional quantitative analysis, improves the precision of permission management, the first complexity reflects the complexity of the project implementation path, the more stages and the more complex the dependency relationship, the higher the requirement for fine-grained control of permissions; the second complexity evaluates the management difficulty on the user side, the more users and the greater the permission difference, the risk of permission conflict grows exponentially; through double-dimensional quantification, the evaluation deviation caused by a single indicator is avoided, and the core challenges of permission management are more comprehensively captured; the weight coefficient is updated iteratively with historical data, adapting to the changes in project management trends; compared with fixed weight, the weight of model training is more objective, reducing subjective error; by comparing the project permission type tendency value with the preset threshold, the permission type is automatically determined as "simple" or "complex", avoiding the subjectivity and time-consuming of manual evaluation; quickly matching the permission management strategy: for example, the multi-role approval process and fine-grained permission control (such as data access isolation by stage) are automatically triggered for complex type projects; the standardized permission template is used for simple type projects to improve efficiency; avoiding excessive configuration of permissions (such as setting complex permission levels for simple projects) or insufficient configuration (such as too coarse granularity of complex project permissions) caused by insufficient experience of managers.

[0072] Specifically, the permission extension module determines to extend the project permission differently when the project has conflict data based on the project permission type and / or the sensitivity of the project conflict data, wherein,

[0073] If the project permission type is a simple permission type and the sensitivity of the project conflict data is less than a preset sensitivity, the permission extension module determines to extend the project permission non-differently.

[0074] If the project permission type is a complex permission type or the sensitivity of the project conflict data is greater than or equal to the preset sensitivity, the permission extension module determines to extend the project permission differently.

[0075] The project conflict data in the embodiment of the present application includes but is not limited to "data inconsistency conflict (for example, the material usage of the same engineering part is different in the design drawing and the construction record), data source conflict (for example, the structural stress data monitored by the sensor in real time deviates from the design specification value beyond the safe range) and permission rule conflict (for example, the high permission user modifies the data and conflicts with the read-only permission of the low permission user)"; the sensitivity of the project conflict data is the ratio of the number of associated stages (the number of stages in which the project conflict data appears) of the project conflict data to a preset number of associated stages, and the preset number of associated stages can be determined by the following method: collecting the historical project data of the same category as the current project, and counting the number of stages in which the conflict data appears in each historical project (i.e., the number of project stages affected or involved by each conflict data);

[0076] For example, a certain conflict data of historical project A involves 2 stages, the same conflict data of project B involves 3 stages, and the same conflict data of project C involves 1 stage; statistical calculation: take the average of the number of associated stages of the conflict data in all historical projects as the preset number of associated stages; for example, in the above example, the average is (2+3+1) / 3=2, so the preset number of associated stages is 2;

[0077] The preset sensitivity can be determined by the following method: collecting the conflict data sensitivity of the historical projects of the same category; obtaining the historical project data of the same type (such as the same industry, size and complexity) as the current project, extracting the sensitivity of each type of conflict data (such as data inconsistency, source conflict, permission rule conflict, etc.) in each project; and summarizing the sensitivity of all historical conflict data, taking the average sensitivity of the historical conflict data as the preset sensitivity, but the above value is not limited thereto, and the person skilled in the art can also adjust the value according to the actual needs.

[0078] The differentiated extension project permission in the embodiment of the application includes extending the highest permission level to a key associated user, and extending a non-highest permission level to a non-key associated user, the key associated user is a direct associated user of project conflict data (an operation user in a creation, modification and approval record of conflict data is taken as a direct associated user), the non-differentiated extension project permission includes synchronously extending access permission to all associated users of project conflict data, the associated user of the project conflict data is a user who has access permission of the project conflict data; the permission level is divided into 1-4 levels, which can be divided by the following method: the decision layer: the highest permission level, which can configure reading and writing of all project data, approval and permission management; the execution layer: the middle-high level permission, which can modify data responsible for the current stage, but needs an approval process; the cooperation layer: the middle level permission, which can upload or view specific data without modification right; the monitoring layer: the low level permission, which can only view data related to the duty, the division method is not unique, and can be determined according to the actual situation of the project.

[0079] It can be understood that a simple type project: few stage divisions, small user cooperation scale, and single permission management demand, and the non-differentiated extension can meet the basic cooperation demand; a complex type project: many stages, frequent cross-department cooperation (such as a large-scale infrastructure project), and a naturally complex permission structure, and the differentiated extension (such as role-based authorization) must be used to reduce the management cost; a high-sensitive conflict (such as a permission rule conflict affecting multiple stages) needs to immediately trigger the differentiated permission extension, for example: sensor data conflict affecting the design + construction stage (sensitivity = 2 / 2 = 1), and only the execution layer is opened to data correction permission, so as to avoid data confusion caused by opening of all permissions; a low-sensitive conflict (such as a single-stage data source conflict) can use the non-differentiated extension to reduce the management cost.

[0080] The application realizes precise permission control based on risk grading, and the permission type and the conflict data sensitivity jointly determine the extension strategy; single permission management is avoided, safety and cooperation efficiency are balanced, the user directly operating from the creation, modification and approval record of conflict data (such as the creator of a design change order and the modifier of a construction log) is given the highest permission preferentially; for example, when the construction record and the design drawing appear material quantity conflict, the direct associated user (the execution layer) can immediately obtain the correction permission, and the problem processing cycle is shortened; the non-key user (the monitoring layer) only obtains basic access permission, and irrelevant personnel is avoided from interfering with conflict solving; the non-differentiated extension (synchronous permission of all personnel) is suitable for a low-risk scene, and the permission configuration workload is reduced; the differentiated extension under a complex type project or a high-sensitive conflict only opens the high permission to necessary users, and system resource consumption is reduced.

[0081] Specifically, the permission recovery module determines whether to recover the extended permission based on whether the project stage changes and / or whether the permission extension user meets a negative access condition, wherein,

[0082] If the project phase changes or the extended permission user meets the negative access condition, the permission recovery module determines to recover the extended permission;

[0083] If the project phase does not change and the extended permission user does not meet the negative access condition, the permission recovery module determines not to recover the extended permission;

[0084] The negative access condition is that the user access interval is greater than the preset access interval.

[0085] The preset access interval in the embodiment of the application is the average value of the implementation time of the same phase of the same project in history, but the above-mentioned value is not limited thereto, and the person skilled in the art can also adjust the value according to actual needs.

[0086] The application is based on the precise recovery of phase change and access behavior. When the project enters the development phase from the design phase, the extended permission of the design phase (such as the modification permission of the design drawing) is automatically recovered. When the project phase iterates, the permission of the old phase is automatically recovered, ensuring that the permission is strictly matched with the current work content, automatically recovering the permission that is no longer needed, reducing the permission audit and maintenance cost, recovering the idle permission to reduce the number of permission records stored by the system, and optimizing the permission verification efficiency. The differentiated extended permission is precisely recovered when the phase changes or the user is idle, forming a closed loop.

[0087] Specifically, the monitoring module is used to determine to mark the multiple-time extended permission user or monitor the change trend of the project conflict data after the extended permission is recovered based on whether there is a multiple-time extended permission user, wherein,

[0088] If there is a multiple-time extended permission user, it is determined to mark the multiple-time extended permission user;

[0089] If there is no multiple-time extended permission user, it is determined to monitor the change trend of the project conflict data after the extended permission is recovered.

[0090] In the embodiment of the application, the multiple-time extended permission user is a user who has more than one extended permission. After the multiple-time users are marked, the system can automatically trigger: permission audit: review the historical permission extension record to analyze whether there is excessive use of permission; permission optimization: include the high-frequency extended permission into the regular permission configuration to reduce repeated extension (such as converting the temporary modification right into the regular editing right); risk warning: increase the approval level when extending the permission subsequently to reduce the risk of abuse.

[0091] It can be understood that the user is extended multiple times, and there may be a permission design defect: the regular permission configuration cannot meet the business needs (such as a frequent need for an engineer to modify permissions, indicating that the initial permission allocation is too strict); business process anomalies: the tasks responsible by the user frequently cause conflicts (such as multiple handling of data inconsistency problems, which may reflect process connection vulnerabilities); and permission abuse risks: high-frequency extension may cause permission boundaries to be blurred, increasing the risk of misoperation or data leakage.

[0092] The application accurately identifies permission design defects, optimizes the permission system, and through audit history extension records, the system can identify high-frequency needs (such as a frequent need for an engineer to access test environment data), convert it to regular permission configuration, and reduce temporary approval processes; the system automatically reviews the permission use records of multiple users, identifies abnormal operations; temporary permissions are automatically recycled and cannot be renewed (renewal is required for continued use); reduce repeated approval overhead, save approval time and labor costs after converting high-frequency extended permissions to regular permissions; reduce dynamic allocation of temporary permissions and reduce the computational complexity of permission verification.

[0093] Specifically, the monitoring module determines whether to perform secondary permission extension based on the change trend of project conflict data after the extended permissions are recycled, wherein

[0094] If the change trend of project conflict data after the extended permissions are recycled is a non-decreasing trend, the monitoring module determines to perform secondary permission extension.

[0095] If the change trend of project conflict data after the extended permissions are recycled is a decreasing trend, the monitoring module determines not to perform secondary permission extension.

[0096] In the embodiment of the application, determining that the change trend of project conflict data after the extended permissions are recycled is a non-decreasing trend includes that the data volume of the project conflict data after the extended permissions are recycled is not reduced, and determining that the change trend of project conflict data after the extended permissions are recycled is a decreasing trend includes that the data volume of the project conflict data after the extended permissions are recycled is reduced; the monitoring module determining to perform secondary permission extension includes extending the permissions to quality inspectors.

[0097] It can be understood that if the conflict data volume is not reduced, it indicates that the effect of the initial permission extension is not sustained, and possible reasons include that the associated process cannot be closed after some users' permissions are recycled (such as quality inspectors without modification rights causing acceptance to stall).

[0098] The application automatically judges whether secondary extension is needed by monitoring the conflict data volume change trend, avoids the hysteresis of manual intervention, and ensures the process closed loop. The non-decreasing trend (such as the conflict data volume being flat or increasing after the permission is recovered) needs to be extended to the quality inspector, and the decreasing trend needs to maintain the status quo to avoid over-authorization. The secondary permission is extended to the quality inspector to solve the common process card point. The secondary extension is only performed when the conflict data is not decreasing to prevent the abuse of permission. The process closed loop problem is solved through the secondary permission extension to reduce the conflict from the source.

[0099] So far, the technical solutions of the application have been described in combination with the preferred embodiments shown in the drawings, but those skilled in the art can easily understand that the protection scope of the application is obviously not limited to these specific embodiments. Those skilled in the art can make equivalent changes or replacements to the related technical features without departing from the principles of the application, and the technical solutions after the changes or replacements will fall within the protection scope of the application.

Claims

1. A multi-source management platform for engineering projects, characterized by: include: The data acquisition module is used to obtain project content information, project implementation process information, and project data source information, and match the project information with the industry standard stage template to obtain project stage information and associated user information for each stage; A data analysis module, connected to the data acquisition module, includes: A first calculation unit is configured to calculate a first complexity based on the number of project division stages and the deviation between the number of edges of the implementation route topology graph and the number of edges of the complete graph; a second calculation unit, configured to calculate a second complexity level based on the number of associated users at each stage and the degree of difference in authority levels of the associated users at each stage; a project authority type analysis unit, connected to the first calculation unit and the second calculation unit, respectively, for calculating a project authority type tendency value based on the first complexity level and the second complexity level, and determining the project authority type based on a comparison result of the project authority type tendency value with a preset project authority type tendency value; A permission extension module, connected to the data analysis module, configured to differentially extend project permissions when determining that conflicting data exists in a project based on the project permission type and / or the sensitivity of the project conflicting data; a permission reclaiming module, connected to the permission extending module, for determining whether to reclaim the extended permission based on whether the project phase has changed and / or whether the permission extended user meets a negative access condition; The monitoring module is connected to the authority recovery module and is used to mark the multiple authority extension users based on whether there are multiple authority extension users when recovering the extended authority or to monitor the change in the project conflict data after the extended authority is recovered.

2. The multi-source management platform for engineering projects according to claim 1, characterized in that: The first calculation unit calculates the first complexity based on the ratio of the number of project division stages to a preset number and the deviation between the number of edges of the implementation route topology graph and the number of edges of the complete graph.

3. The multi-source management platform for engineering projects according to claim 2, characterized in that: The second calculation unit calculates the second complexity based on a ratio of the number of associated users in each stage to a preset number of associated users and a ratio of a difference degree of authority levels of associated users in each stage to a preset difference degree.

4. The multi-source management platform for engineering projects according to claim 3, characterized in that: The project authority type analysis unit calculates a project authority type tendency value based on the product of the first complexity and its weight coefficient and the product of the second complexity and its weight coefficient.

5. The multi-source management platform for engineering projects according to claim 4, characterized in that: The project authority type analysis unit determines the project authority type based on a comparison result of the project authority type tendency value and a preset project authority type tendency value, wherein: If the project authority type tendency value is greater than or equal to the preset project authority type tendency value, the project authority type analysis unit determines that the project authority type is a complex project authority type; If the project authority type tendency value is less than a preset project authority type tendency value, the project authority type analysis unit determines that the project authority type is a simple project authority type.

6. The multi-source management platform for engineering projects according to claim 5, characterized in that: The permission extension module determines that when a project has conflicting data, it differentially extends the project permission based on the project permission type and / or the sensitivity of the project conflicting data, wherein: If the project permission type is a simple permission type and the sensitivity of the project conflict data is less than a preset sensitivity, the permission extension module determines to extend the project permission in a non-differentiated manner; If the project permission type is a complex permission type or the sensitivity of the project conflict data is greater than or equal to the preset sensitivity, the permission extension module determines to differentially extend the project permission.

7. The multi-source management platform for engineering projects according to claim 6, characterized in that: The sensitivity of the project conflict data is determined according to the number of associated stages of the project conflict data.

8. The multi-source management platform for engineering projects according to claim 7, characterized in that: The permission recovery module determines whether to recover the extended permission based on whether the project phase has changed and / or whether the permission extension user meets the negative access condition, wherein: If the project phase changes or the permission-extended user meets the negative access condition, the permission-reclaiming module determines to revoke the extended permission; If the project phase has not changed and the permission-extended user does not meet the negative access condition, the permission reclaiming module determines that the extended permission does not need to be reclaimed; The negative access condition is that the user access interval is greater than a preset access interval.

9. The engineering project multi-source management platform according to claim 8, characterized in that: The monitoring module is used to determine and mark the multiple permission extension user based on whether there is a multiple permission extension user when reclaiming the extended permission or to monitor the change trend of the project conflict data after the extended permission is reclaimed, wherein, If there are multiple permission extension users, make sure to mark the multiple permission extension users; If there are no users with multiple permission extensions, determine the changing trend of the project conflict data after monitoring the recovery of extended permissions.

10. The engineering project multi-source management platform according to claim 9, characterized in that: The monitoring module determines whether to perform a second permission extension based on the change trend of the project conflict data after the extended permission is recovered, wherein: If the change trend of the project conflict data after the extended authority is recovered is a non-decreasing trend, the monitoring module determines to perform a second authority extension.

Images