A project management system and method based on multi-dimensional information association

CN122243388APending Publication Date: 2026-06-19HITACHI BUILDING TECH GUANGZHOU CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
HITACHI BUILDING TECH GUANGZHOU CO LTD
Filing Date
2026-03-13
Publication Date
2026-06-19

Smart Images

  • Figure CN122243388A_ABST
    Figure CN122243388A_ABST
Patent Text Reader

Abstract

This application relates to a project management method and system based on multi-dimensional information association, belonging to the field of project management technology. It includes: an information association engine, a permission control center, a full-lifecycle information management module, a customer project information query module, and a customer project information push module. It constructs a four-dimensional association model of customer-project-contact-file through three technologies, combining triggered synchronization and timed verification to ensure data consistency; establishes a four-level permission system to achieve fine-grained data isolation and seamless switching across projects; supports multi-condition combined retrieval and optimizes query efficiency through caching; and incorporates an intelligent reminder decision tree model to dynamically adjust push strategies based on multi-dimensional attributes, providing precise and customized reminders through multiple channels. By building an association model, synchronizing and updating data, implementing refined permission management, optimizing retrieval, and intelligent push, it solves the problems of information silos and loose permissions in traditional management, improving the efficiency of multi-project management and the quality of customer service.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of project management technology, and in particular to project management systems and methods based on multi-dimensional information association. Background Technology

[0002] With the accelerated development of smart cities, the cloud platform building services industry is undergoing a profound digital transformation. Customer projects in commercial buildings, industrial parks, and smart communities exhibit significant characteristics such as "multiple application services interconnected, frequent cross-departmental collaboration, and large differences in contract cycles." Platform operators need to simultaneously manage multiple complex processes, including customer information registration, archiving of various project documents, cross-site service inquiries, and tiered customer renewal follow-up.

[0003] However, the industry currently predominantly employs a decentralized management model. According to research, as many as 78% of companies still store customer information in CRM systems, archive project documents on FTP servers, and rely on Excel spreadsheets for contract management, resulting in severe information fragmentation. This traditional two-dimensional (e.g., "customer-project") management model struggles to achieve deep integration of core elements such as contacts and project documents, especially in scenarios involving the parallel management of multiple projects, exhibiting the following technical shortcomings: Information silos lead to low collaboration efficiency: Traditional systems often achieve simple "customer-project" associations, failing to cover deep integration of contacts and project documents. For example, in a typical smart industrial park scenario, after the property service contract of Building A changes, its contact information is updated in the CRM. However, because the CRM system is not linked to the file system storing central air conditioning maintenance records, the old information in the maintenance record file fails to synchronize. When Building B, which shares the same central air conditioning system, experiences a sudden malfunction, maintenance personnel cannot contact the person in charge of Building A in a timely manner based on the old contact information in the erroneous file, delaying cross-site collaborative repairs and causing potential equipment damage. This case clearly illustrates that information silos directly increase the risk of service interruption, requiring on-site maintenance personnel to operate across multiple systems to retrieve project documents, increasing time consumption.

[0004] Information consistency is difficult to guarantee: When customer basic information or project information changes, it needs to be repeatedly modified in multiple isolated systems, which easily leads to information inconsistency. Most enterprises therefore face the problem of information inconsistency, which directly affects the quality of customer service and the accuracy of decision-making. At the same time, most enterprises still rely on manual monitoring of contract expiration dates, resulting in a 1.8 times higher rate of missed reminders for high-value customers than for ordinary customers, thus causing an average annual customer churn rate of 8%-12%.

[0005] Lax access control poses data security risks: Traditional systems employ a broad role-based access control approach, failing to achieve dual isolation between "functional modules" and "data scope." In the aforementioned park case, the project administrator, due to their role permissions, gained viewing access to "all projects in the park," but this also allowed them to access confidential commercial data from other buildings, exposing a serious risk of information leakage. Furthermore, when managing multiple projects, switching permissions often requires re-login, increasing operational time and severely impacting management efficiency.

[0006] Information retrieval efficiency is low and cannot meet complex query needs: Existing systems mostly support single-condition queries and do not support combined searches based on key dimensions such as "service site ID + file category + contract validity period". In building service scenarios, finding specific project implementation documents for a particular park takes a long time on average, resulting in extremely low retrieval efficiency and failing to meet the need for rapid decision-making.

[0007] In summary, in the specific field of cloud platform building integrated services, the general architecture of traditional project management systems can no longer adapt to the pain points of segmented scenarios such as chaotic association of multiple application services, inefficient cross-project collaboration, and insufficient hierarchical customer renewal management. There is an urgent need for an intelligent management system that can achieve intelligent association of multi-dimensional information, automated service reminders, and refined permission control. Summary of the Invention

[0008] To address or partially address the problems existing in related technologies, this application provides a project management system and method based on multi-dimensional information association, aiming to solve the problems of chaotic association of multiple application services, inefficient cross-project collaboration, and insufficient hierarchical customer renewal management in traditional project management systems.

[0009] The first aspect of this application provides a project management system based on multi-dimensional information association, including: A project management system based on multi-dimensional information association, characterized in that it includes: Information association engine, access control center, full-cycle information management module, customer project information query module, and customer project information push module; The full-cycle information management module is used to integrate customer basic information, project contract information, contact information and multi-format project files, and provides full-process management of information entry, storage, update and version control, and supports automatic synchronization and verification of information changes; The permission control center is used to establish a four-level permission control system of user-role-functional module-data scope. Through row-level data isolation and fine-grained configuration of module operation permissions, it enables secure access and flexible switching of data across projects and sites. The information association engine is used to build and maintain the association system of customers-projects-contacts-files. It adopts three technologies: primary keyword binding, association index mapping and semantic intelligent matching to achieve deep association and real-time synchronization of cross-dimensional data and support efficient processing of tens of millions of data volumes. The customer project information query module is used to receive multi-dimensional combined query requests, provide a retrieval method that combines precise query and fuzzy query, and realize one-click jump to query results and multi-dimensional data association display; The customer project information push module is used to automatically trigger and accurately deliver customized reminder messages based on project contract attributes and customer classification information through multiple push channels. Each module achieves collaborative operation through a distributed data interaction protocol, adapting to the multi-project management needs of cloud platform building integrated service scenarios.

[0010] Optional, information association engines include: The system includes a model management unit, a synchronization update unit, and a data verification unit. The association model management unit is used to build and maintain a four-dimensional association relationship of "customer-project-contact-file". It realizes data association through a triple association method of primary key, association index and semantic mapping. It establishes an association index table of project, contact and file through the unique identifier of customer, and then builds exclusive association fields between application service and project. The semantic mapping technology is based on TF-IDF algorithm and cosine similarity calculation. The synchronization update unit adopts a dual mechanism of triggered synchronization and timed verification. When any dimension information changes, it triggers the synchronous update of the associated data, and the synchronization scope covers the relevant records of all associated dimensions. The data verification unit periodically performs full data consistency verification, focusing on verifying the consistency between contact information and project files, and the matching of application service validity period and contract validity period, to ensure data accuracy.

[0011] Optionally, the access control center includes: Permission configuration unit and access control unit; The permission configuration unit supports multiple role configurations such as super administrator, project administrator, and ordinary operator. It can be refined to specific operation permissions such as file viewing / editing / downloading, read-only / modification of customer information, and access to application service data. The data access scope can be further subdivided according to the region to which the project belongs and the type of application service. The access control unit establishes a permission mapping relationship based on user ID and project ID, and uses SQL statements to dynamically construct permission filtering conditions to achieve data isolation. It supports seamless switching between multiple authorized projects without requiring users to log in again, and the permission loading time is no more than 1 second.

[0012] Optionally, the full-cycle information management module includes: Customer information management module and customer project document management module; The customer information management module is used to input and store basic customer information, project information, and contact information, and supports data verification. Basic customer information includes customer name, customer category, region, project address, customer number, and account configuration information. Project information includes contract number, contract validity period, contract status, application service association information, service status, and project file association information; application service association information supports multi-site service binding. Contact information includes customer contact information and internal contact information. Customer contact information includes the names, phone numbers, and email addresses of at least two groups of contacts; internal contact information is stored by department and supports contact priority settings, with push notifications sent in priority order. The customer project file management module supports uploading, adding, deleting, and downloading various file formats such as Word, Excel, PPT, PDF, drawings, and images. It enables precise association between files and projects and application services, and allows for traceability and management based on the modifier, file category, and upload time. It also features file version control functionality.

[0013] Optionally, the customer project information query module supports combined retrieval of multiple query conditions such as contract number, project name, service site ID, customer category, contract validity period, and document category, and can arbitrarily combine 2-6 query conditions; We employ three optimization techniques to improve query response efficiency: caching popular query results in Redis, creating composite indexes on key fields, and loading query results in pages. The query results include basic customer information, project contract information, contact information, associated file information, and application service status. It supports one-click jump to the corresponding details page. The query list supports sorting by any field and Excel export function, exporting data content of different dimensions.

[0014] Optionally, the customer project information push module includes: Push rule configuration unit, message template unit, and push execution unit; The push rule configuration unit allows for custom push rules based on dimensions such as project type, project importance, customer type, customer level, contract amount, and service type. It also allows for setting multi-level push strategies, including advance trigger time, repeated push interval, and expedited reminders. The message template unit provides multiple preset templates for renewal reminders, service changes, and maintenance notices. It also supports user-defined template content and allows the insertion of dynamic variables, drawings, attachments, and jump links. The push execution unit integrates four major push channels: in-site messages, WeChat, SMS, and email. It supports both batch push and single-point push modes, records push time, recipients, push status, and open rate, and performs secondary pushes for undelivered messages.

[0015] Optionally, the customer project information push module has a built-in intelligent reminder decision tree model that dynamically adjusts the push strategy based on the multi-dimensional attributes of the project and the customer. For enterprise clients, high-importance clients, important clients with contract amounts exceeding a certain amount, and long-term service clients, the frequency of push notifications is increased compared to ordinary clients, the number of days in advance for expedited reminders is increased, and a multi-level push strategy is set up with triggering X days in advance, repeating at Y-day intervals, and expedited reminders Z days before the due date, prioritizing WeChat and SMS push channels; For individual clients, projects of average importance, with contract amounts less than a certain amount, and for short-term services, set up two push notifications that are triggered X days in advance and repeated Y days apart, using SMS and in-site message push channels.

[0016] The second aspect of this application provides a project management method based on multi-dimensional information association, including: The system retrieves basic customer information, project contract information, project-related documents, and contact information from the database to generate a unique customer ID. It then establishes a four-dimensional association model of customer-project-contact-file using primary keys, association indexes, and semantic mapping to link disparate data entities. Specifically, basic customer information includes the customer name, category, region, and address; project contract information includes contract number, validity period, service status, and customer and internal department contact information, automatically associated with the customer ID; and project-related documents are uploaded, generating file IDs that are then associated with the project ID and application service ID. When any dimension of information changes, the associated data is synchronously updated according to predefined association rules, covering all related items, contact records, and file attributes; at the same time, full data verification is performed regularly to compare and repair inconsistencies, ensuring that multi-dimensional information is always consistent; and all change operation logs are recorded for audit traceability. Access control and data isolation are based on a four-level access model of user-role-module-data, allowing for fine-grained access permission configuration. Users can seamlessly switch between different projects based on the list of authorized project IDs. Access filtering conditions are dynamically constructed using SQL to ensure that users can only access data in authorized projects. Searches can be performed using multiple conditions such as contract number, project name, service site ID, customer category, validity period, and file category. The query results are optimized using caching, indexing, and pagination techniques, presenting comprehensive information on customers, projects, contacts, and related files, and providing links to detailed information about the query results. Based on the project contract validity period, and combined with multiple dimensions such as customer level, project importance, contract amount, and service type, a reminder strategy is dynamically set. Projects to be reminded are automatically filtered through preset rules, and customized reminder content is pushed according to contact priority and preferred channels to ensure that no key nodes are missed. Based on the project contract validity period, and combined with multiple dimensions such as customer level, project importance, contract amount, and service type, a reminder strategy is dynamically set. Projects to be reminded are filtered by preset rules such as advance notice days, repetition frequency, and expedited thresholds. Customized reminder content is pushed according to contact priority and preferred channels to ensure that no key milestones are missed.

[0017] Optionally, establishing the four-dimensional relationship model of customer-project-contact-file includes: Establish associated index records for projects, contacts, files, and application services, using the customer's unique identifier as the primary key; Through semantic intelligent matching technology, intelligent recognition and association of customer name aliases, project abbreviations, and file categories can be achieved; A database sharding and table partitioning strategy is adopted, with related data stored in separate databases based on the project's location and in separate tables based on the contract's validity period, ensuring efficient response to related queries.

[0018] Optionally, the access control and data isolation include: The super administrator assigns roles to users and configures corresponding functional module operation permissions for each role. Specific data access scopes can be configured for each user, and can be further subdivided by project, region, and application service type; After a user logs into the system, the access control unit dynamically filters data based on permission mapping relationships, displaying only information within the user's authorized scope. When a user switches projects, the permission configuration for the corresponding project is automatically loaded.

[0019] The technical solution provided in this application may include the following beneficial effects: Through the collaborative operation of five modules—information association engine, access control center, full-cycle information management, intelligent query, and intelligent push—the system achieves deep integration and real-time synchronization of multi-dimensional information such as customers, projects, contacts, and files, solving the problem of information silos. Simultaneously, relying on a four-level access control system, it enables row-level data isolation and seamless switching across projects, ensuring data security and operational convenience. Based on multi-dimensional attributes, it dynamically adjusts reminder strategies and delivers information accurately through multiple channels, improving the control capabilities for key nodes such as contract renewals, and comprehensively optimizing management efficiency and customer service quality in multi-project parallel scenarios.

[0020] A four-dimensional association model is constructed using primary keys, related indexes, and semantic mapping. Triggered synchronization and timed verification mechanisms ensure data consistency, resolving the problem of asynchronous information changes. Dynamic SQL permission filtering based on a four-level permission model enables fine-grained data isolation and flexible switching across projects. Multi-condition combined retrieval and caching optimization technologies significantly improve information query efficiency. The built-in intelligent reminder decision tree dynamically adjusts push strategies based on factors such as customer level and contract amount, ensuring the timeliness and accuracy of key reminders, providing reliable technical support for intelligent management throughout the project lifecycle.

[0021] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0022] The above and other objects, features and advantages of this application will become more apparent from the more detailed description of exemplary embodiments thereof in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments thereof.

[0023] Figure 1 This is a schematic diagram of the structure of a project management system based on multi-dimensional information association, as shown in an embodiment of this application; Figure 2 This is a schematic diagram of a multi-dimensional information association model for a project management system based on multi-dimensional information association, as shown in an embodiment of this application. Figure 3 This is a schematic diagram illustrating the information synchronization and update process of a project management system based on multi-dimensional information association, as shown in an embodiment of this application. Figure 4 This is a schematic diagram of the permission management matrix structure of a project management system based on multi-dimensional information association, as shown in an embodiment of this application. Figure 5 This is a schematic diagram of the intelligent push system workflow of a project management system based on multi-dimensional information association, as shown in an embodiment of this application. Figure 6 This is a schematic diagram illustrating the intelligent query and result display of a project management system based on multi-dimensional information association, as shown in an embodiment of this application. Detailed Implementation

[0024] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While embodiments of this application are shown in the drawings, it should be understood that this application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to make this application more thorough and complete, and to fully convey the scope of this application to those skilled in the art.

[0025] The technical solutions of the embodiments of this application are described in detail below with reference to the accompanying drawings.

[0026] In some implementations, see Figure 1 A project management system based on multi-dimensional information association, comprising: Information association engine, access control center, full-cycle information management module, customer project information query module, and customer project information push module; The full-cycle information management module is used to integrate customer basic information, project contract information, contact information and multi-format project files, and provides full-process management of information entry, storage, update and version control, and supports automatic synchronization and verification of information changes.

[0027] Specifically, the full-cycle information management module includes: Customer information management module and customer project document management module; The customer information management module includes: a customer basic information management unit, a project information management unit, and a contact person management unit.

[0028] The customer basic information management unit is used to input and store customer name, customer category, region, project address, customer number, and account configuration information, and supports data verification. The project information management unit is used to input and store contract number, contract validity period, contract status, application service association information, service status, and project file association information. The contract validity period supports automatic calculation and display, and the application service association information supports multi-site service binding.

[0029] The contact management unit is used to input and store customer contact information and internal contact information. The customer contact information includes the names, phone numbers and email addresses of at least two groups of contacts. The internal contact information is stored in categories such as sales department, engineering and technical department, on-site maintenance department, and technical department. It supports setting contact priority and pushes reminders in priority order.

[0030] The permission control center is used to establish a four-level permission control system of user-role-functional module-data scope. Through row-level data isolation and fine-grained configuration of module operation permissions, it enables secure access and flexible switching of data across projects and sites.

[0031] Specifically, the permission management center includes: Permission configuration unit and access control unit; The permission configuration unit supports assigning roles to users, such as super administrator, project administrator, and ordinary operator, and configuring module access permissions for each role. For example, one or more functional modules can be selected, and module permissions can be refined to specific operation permissions such as file viewing / editing / downloading, read-only / modification of customer information, and access to application service data.

[0032] The access control unit establishes a permission mapping table based on user ID and project ID, uses row-level permission control technology to achieve cross-project permission isolation, dynamically concatenates permission filtering conditions through SQL statements, supports users to associate with multiple projects at the same time, and seamlessly switch between different projects without having to log in again, and the permission loading time is ≤1 second.

[0033] The information association engine is used to build and maintain a relationship system between customers, projects, contacts, and files. It adopts three technologies: primary keyword binding, association index mapping, and semantic intelligent matching to achieve deep association and real-time synchronization of cross-dimensional data, and supports efficient processing of tens of millions of data volumes.

[0034] Specifically, it includes a model management unit, a synchronization update unit, and a data verification unit; The association model management unit is used to maintain a four-dimensional association relationship of "customer-project-contact-file". The association relationship table is designed to include fields such as customer number, project ID, contact ID, file ID, application service ID, association type, association timestamp, and updater. It adopts a database sharding and table sharding strategy, with databases sharded by project location and tables sharded by contract validity period. Data association is achieved through a triple association method of "primary key + association index + semantic mapping". The semantic mapping technology is based on the TF-IDF algorithm and cosine similarity calculation to achieve intelligent matching of customer name aliases, project abbreviations, and common names of file categories. Using the customer number as the primary key, an association index table of project ID, contact ID, and file ID is established. For building service scenarios, an association field of "application service ID-project ID" is added to achieve accurate binding of services across multiple sites. Through semantic mapping technology, traditional problems such as "historical files cannot be retrieved after customer name changes" and "association failure due to inconsistency between project abbreviation and full name" are solved, improving the efficiency of unstructured data association by 300%.

[0035] The synchronization update unit employs a dual mechanism of "triggered synchronization + timed verification." When key information such as customer address or project service status changes, it automatically triggers the synchronization update of related data. The synchronization scope covers project information, contact association records, and related file attributes. It supports a response time of ≤500ms for related queries with tens of millions of data points, achieving "one-time modification, multiple-time synchronization" and avoiding information inconsistency issues.

[0036] The data verification unit performs full data verification every day at midnight, focusing on verifying the consistency between "on-site contact information and project files" and "matching of application service validity period and contract validity period" for building service scenarios, ensuring 100% data consistency and reducing the error rate by 98% compared to the traditional single synchronization mechanism.

[0037] The customer project information query module is used to receive multi-dimensional combined query requests, provide a retrieval method that combines precise query and fuzzy query, and realize one-click jump to query results and multi-dimensional data association display.

[0038] Specifically, the customer project information query module supports combined retrieval of multiple query conditions, including contract number, project name, service site ID, customer category, contract validity period, and file category, allowing for any combination of 2-6 query conditions. It employs three optimization techniques: Redis caching of popular query results, creation of key field composite indexes, and paginated loading of query results, to improve query response efficiency. Query results include basic customer information, project contract information, contact information, associated file information, and application service status. It supports one-click navigation to the corresponding details page, and the query list supports sorting by any field and Excel export functionality, allowing export of data content across different dimensions.

[0039] The customer project information push module is used to automatically trigger and accurately deliver customized reminder messages based on project contract attributes and customer classification information through multiple push channels.

[0040] Specifically, the customer project information push module includes: The system includes an intelligent reminder decision tree algorithm, a push rule configuration unit, a message template unit, and a push execution unit. The push rule configuration unit allows for custom push rules based on project type, project importance, customer type, customer level, contract amount, and service type. It supports custom decision-making push rules based on project type (commercial building / industrial park / smart community), project importance (high / medium / low), customer type (enterprise / individual), customer level (VIP / regular), service type (long-term / short-term), and contract amount (≥1 million / 500,000~1 million / <500,000). It allows for setting multi-level push strategies, including advance trigger time, repeat push intervals, and expedited reminders. For example, a multi-level push strategy of "trigger X days in advance + repeat at Y days interval + expedited reminder Z days before expiration" can be set. For instance, a VIP customer long-term service contract could be set to "first push 30 days in advance + repeat at 7 days interval + expedited reminder 3 days before expiration," while a regular customer short-term contract could be set to "first push 15 days in advance + repeat at 5 days interval." It also supports setting push priorities by customer level (VIP customers receive priority) and setting push frequency by contract amount (higher-value contracts receive more pushes), reducing the missed reminder rate to 0 compared to traditional fixed-rule pushes.

[0041] The message template unit provides a template library containing preset templates for 10 building service scenarios, including renewal reminders, service changes, document notifications, and maintenance notifications. It supports user-defined template variables, such as application service names and project site addresses. Templates support text editing, drawing insertion, and uploading of maintenance record attachments. Links can redirect to the system project details page, document download page, or personnel contact information page.

[0042] The push execution unit integrates four major push channels: in-site messages, WeChat, SMS, and email. It adapts to different channel protocols through a unified push interface, such as WeChat API, SMS gateway protocol, and SMTP protocol. It supports both batch push and single-point push modes, records push time, recipient, push status, and open rate, and performs secondary push for undelivered messages.

[0043] The intelligent reminder decision tree algorithm dynamically adjusts the reminder strategy based on six dimensions: project type (commercial building / industrial park / smart community), project importance (high / medium / low), customer type (enterprise / individual), customer level (VIP / regular), service type (long-term / short-term), and contract amount (≥1 million / 500,000~1 million / <500,000). Among them, VIP customers with high importance, high amount, and long-term service receive 50% more push notifications than regular customers, and the advance notice period for expedited reminders is doubled.

[0044] In some implementations, corresponding to the aforementioned application function implementation system embodiments, this application also provides a project management method based on multi-dimensional information association and corresponding embodiments.

[0045] A project management method based on multi-dimensional information association includes: S201. Retrieve customer basic information, project contract information, project-related documents, and contact information from the database to generate a unique customer number. Establish a four-dimensional association model of customer-project-contact-file through primary key, association index, and semantic mapping to link the scattered data entities. Specifically, basic customer information includes entering the customer's name, category, region, and address; project contract information includes the contract number, validity period, service status, customer and internal department contact information, and automatically associates the customer number; upload project-related files, generate file IDs, and associate them with the project ID and application service ID; The establishment of the four-dimensional relationship model of customer-project-contact-file includes: The customer information management module calls and generates a unique customer number, and enters information such as customer name, category, region, and address; enters contract number, validity period, service status, etc., and the system automatically associates it with the customer number; enters customer and internal contact information for multiple departments and sets priorities; The customer project file management module uploads file information, including project-related files such as design drawings and maintenance records, generates file IDs, and associates them with project IDs and application service IDs. The association model is constructed by using a three-pronged approach of primary key + association index + semantic mapping to establish a four-dimensional association model of "customer-project-contact person-file", while also performing intelligent matching of aliases and abbreviations.

[0046] S202. When any dimension of information changes, the associated data is synchronously updated according to predefined association rules, covering all related items, contact records, and file attributes; at the same time, full data verification is performed regularly to compare and repair inconsistencies, ensuring that multi-dimensional information is always consistent; all change operation logs are recorded for audit traceability. Specifically, a dual mechanism of triggered synchronization and timed verification is adopted. When key information such as customer address and project service status changes, the information association engine automatically triggers the synchronization and update of related data, covering project information, contact association records, and related file attributes. A full data verification is performed every day at midnight, with a focus on verifying the consistency between "on-site contact information and project files" and "matching of application service validity period with contract validity period" for building service scenarios, ensuring 100% data consistency. S203, access control and data isolation, based on a four-level access control model of user-role-module-data, allows for fine-grained access control configuration. Users can seamlessly switch between different projects based on the list of authorized project IDs. By dynamically constructing access control filtering conditions using SQL, it ensures that users can only access the data of authorized projects. Specifically, a four-level permission matrix of "user-role-module-data" is constructed, supporting the combined configuration of 5 types of roles, 5 major functional modules, and 3 levels of data permissions. It can be refined to specific operation permissions for building service scenarios such as file viewing / editing / downloading, read-only / modification of customer application service information, and maintenance record upload permissions. For cross-regional multi-project management scenarios, it supports the allocation of data permissions by region. For example, the administrator of region XX can only access project data in that region and cannot view sensitive information of projects in North China.

[0047] The cross-project switching mechanism establishes a permission mapping table based on user ID and project ID. Users can seamlessly switch to authorized projects via the project switching menu without needing to log in again. Permission loading time is ≤1 second, improving efficiency. It supports simultaneous association with multiple projects, adapting to scenarios requiring the management of multiple industrial park projects simultaneously, further enhancing operational efficiency.

[0048] Access control technology employs row-level access control and dynamically constructs access filtering conditions using SQL statements to ensure that users can only access data in authorized projects. The access verification pass rate is 100%, effectively preventing information leakage. For building service scenarios, application service data isolation has been added. For example, only engineering and technical personnel can access project drawings, and on-site maintenance personnel can only view maintenance records and simple project information. The risk of customer information leakage is reduced compared to traditional, coarse-grained access control systems.

[0049] S204 allows for arbitrary combinations of multiple conditions for retrieval based on contract number, project name, service site ID, customer category, validity period, and file category; the query results employ caching, index optimization, and pagination loading optimization technologies, presenting comprehensive information on customers, projects, contacts, and related files, and constructing detailed information links for the query results; Specifically, the multi-condition combination query supports the combination of six types of query conditions, including contract number (exact query), project name (fuzzy query), service site ID (exact query), customer category (type selection), contract validity period (time range), and document category (multiple selection). You can combine any 2 to 6 conditions.

[0050] The query results cover a full range of data, including customer information, project details, contacts, and associated files. The query results list supports one-click navigation, such as clicking on a customer's name to jump to the customer information details page, clicking on a file name to jump to the file download page, clicking on a contact person to jump to the contact information display page, and clicking on the application service ID to jump to the service status details page.

[0051] The query optimization technology employs query caching, using Redis to cache popular query results with a cache validity period of 1 hour, index optimization, creating composite indexes for key query fields, and pagination loading, with a default of 20 records per page and a maximum support of 100 records per page, to solve the problem of excessively long file retrieval times in building service scenarios.

[0052] S205. Based on the project contract validity period, and combined with multiple dimensions such as customer level, project importance, contract amount, and service type, dynamically set reminder strategies, automatically filter projects to be reminded through preset rules, and push customized reminder content according to contact priority and preferred channels to ensure that no key nodes are missed. Specifically, it integrates four major push channels: in-site messaging, WeChat, SMS, and email. It adapts to different channel protocols through a unified push interface, such as WeChat API, SMS gateway protocol, and SMTP protocol. It can perform batch pushes, such as service upgrade notifications for all customers in a certain park, and single-point pushes, such as renewal reminders for VIP customers, to improve the success rate of pushes.

[0053] The dynamic rule engine, through an intelligent reminder decision tree model, dynamically adjusts the push strategy based on multi-dimensional attributes of projects and customers: Custom push rules are set based on project type (commercial building / industrial park / smart community), project importance (high / medium / low), customer type (enterprise / individual), customer level (VIP / regular), service type (long-term / short-term), and contract amount (≥1 million / 500,000~1 million / <500,000). A multi-level push strategy can be set, such as "triggered X days in advance + repeated every Y days + expedited every Z days before expiration." For example, a long-term service contract for a VIP customer can be set to "first push 30 days in advance + repeated every 7 days + expedited every 3 days before expiration," while a short-term contract for a regular customer can be set to "first push 15 days in advance + repeated every 5 days." Push priority is set by customer level, and push frequency is set by contract amount, with higher-value contracts receiving more pushes. Compared to traditional fixed-rule pushes, the missed reminder rate is reduced to 0.

[0054] It provides a template library containing preset templates for 10 building service scenarios, including renewal reminders, service changes, document notifications, and maintenance notices. It also supports user-defined template variables, such as {application service name} and {project site address}. Templates support text editing, drawing insertion, and uploading of maintenance record attachments. Links can redirect to the system's project details page, document download page, or personnel contact information page.

[0055] S206. Based on the project contract validity period, and combined with multiple dimensions such as customer level, project importance, contract amount, and service type, dynamically set reminder strategies. Filter projects to be reminded by preset rules such as advance notice days, repetition frequency, and expedited thresholds, and push customized reminder content according to contact priority and preferred channels to ensure that no key nodes are missed.

[0056] Specifically, through the intelligent reminder decision tree algorithm built into the dynamic push module, the push strategy is dynamically adjusted based on the multi-dimensional attributes of the depression project and the client: for corporate clients, high-importance clients, VIP clients with contract amounts ≥ 1 million and long-term service, the push frequency is increased by 50% compared to ordinary clients, the advance notice period for expedited reminders is doubled, and three pushes are set up in advance: 30 days, 15 days, and 7 days in advance, with priority given to WeChat + SMS push channels. For individual clients, projects of average importance, with contract amounts less than 500,000 and short-term services, we will send two push notifications 15 days and 7 days in advance, using a combination of SMS and in-app messages.

[0057] In some implementations, corresponding to the aforementioned application function implementation system and method embodiments, this application also provides a specific implementation process example of a project management system based on multi-dimensional information association, including: 1. Specific implementation of each module: Implementation of the permission management center: The super administrator logs into the BIVALE platform user center and assigns permissions to system users through the super administrator authorization unit. For building service scenarios, exclusive permissions such as "application service data access", "file download" and "park project data viewing" can be granted.

[0058] The access control unit establishes a permission mapping table based on user ID and project ID. For users managing multiple regions, more detailed permissions can be configured. When a user accesses the system, the system verifies their permission mapping table and only allows access to information related to authorized projects, thus achieving cross-project permission isolation.

[0059] Implementation of the Customer Information Management Module: After authorized users log in to the system, they enter the "Customer Information Management" interface. Through the Customer Basic Information Management unit, they enter customer name, customer category, region, project address, customer number, and account configuration information, which is then stored in the SQL database. Through the Project Information Management unit, they enter contract number, contract validity period (after the user enters the start date, the system automatically calculates and displays the total duration and expiration date), contract status (e.g., effective, pending, expired), application service association information (selecting application services already online on the platform), and service status. Simultaneously, they associate the contract with the file ID from the Project File Management module to establish information association. Through the Contact Management unit, they enter the names, phone numbers, and email addresses of Customer Contact 1 and Contact 2, as well as contact information for internal departments such as sales, engineering, on-site maintenance, and technical departments, storing these information in the database. The system supports setting priority levels 1-3 for customer contacts, with push notifications sent in priority order, with level 1 contacts receiving the highest priority.

[0060] Implementation of the Customer Project Document Management Module: Authorized users access the "Project Document Management" interface and select the platform site application services associated with the current project through the application service management unit. The system stores the association between the application service ID and the project ID. Users can upload requirements survey documents, design documents, engineering implementation documents, etc., through the document management unit, supporting formats such as Word, Excel, PPT, PDF, JPG, and PNG. Upon upload, the system automatically records the file category, file name, uploader (currently logged-in user), and upload time, generating a unique file ID, which is then associated with the project ID and application service ID. Users can add, delete, and download uploaded files through the document management unit, and can also search for files by file category, file name (fuzzy search), or the person who modified them.

[0061] Implementation of the Customer Project Information Query Module: Authorized users access the "Project Information Query" interface and enter query criteria, such as contract number, project name, and service site ID. Users can enter a single criterion or a combination of multiple criteria. After receiving the query criteria, the system queries the database using SQL statements, linking the customer information table, project information table, contact information table, and file information table. The system then returns a list of query results, containing information such as customer name, contract number, project name, service status, expiration date, contact person, associated file name, and application service status. Users can click on the customer information, file information, or contact information options in the list to navigate to the corresponding details page in the customer information management module, project file management module, or contact management unit.

[0062] Implementation of the Customer Project Information Push Module: Authorized users access the "Information Push Management" interface and select a preset renewal reminder template through the message template unit, such as "[BIVALE Platform] Your project (Contract No.: XXX) will expire in X days. Please renew in time." Users can also customize template content and save it. Through the push settings unit, users can select the push method, including multiple options such as internal messages, WeChat, SMS, and email, and select the push recipients, such as Customer Contact 1, Contact 2, and contacts from the company's internal sales department and on-site maintenance department. Through the scheduled task unit, push rules can be set: the initial push can be triggered X days in advance, with repeat pushes every Y days until the contract expires. Users can manually enable or disable the push function. The system backend deploys scheduled tasks that execute every 24 hours, querying the database for projects with near-expiration contracts. If the push trigger conditions are met, the corresponding push interface, such as WeChat API, SMS gateway, or email server interface, is called to push the reminder message to the specified contact.

[0063] Implementation of the information association engine: Information association matrix design: Information association table, containing the following fields: customer_id (customer ID); project_id (project ID); contact_id (Contact ID); file_id (file ID); relation_type (relationship type); relation_time (relation time); update_user (update user); When the information association engine detects data changes, it performs the following steps: Information change trigger: When key information such as customer address and project service status changes in the customer information management module; Related queries: The system queries the related tables based on customer_id to obtain all related project_ids; Data Update: The system updates customer information and application service binding information for all related projects; File association update: The system updates the file information of all associated items; Log recording: The system records change logs, including the change time, the person making the change, the content of the change, and the number of related updated files / projects, for auditing and problem tracking.

[0064] 2. Multi-dimensional information association mechanism: Linking Customer Information with Project Information: When basic customer information (customer name, alias, customer category, customer number, region, and project address) is entered in the customer information management module, the system automatically creates a project information association entry for that customer. For building service scenarios, a new "batch application service association" function has been added, allowing services from multiple sites to be bound at once. When contract information (contract number, contract validity period, contract status, and contract transition period) is entered in the project information management module, the system automatically associates the basic customer information, achieving intelligent "customer-project" association. Simultaneously, it verifies the matching of application service validity periods with contract validity periods to avoid "service expiration and non-renewal" issues. The application service association and customer account association functions in the project information management module automatically associate the corresponding service status and validity period, supporting "filtering associated projects by application service type."

[0065] Customer information and contact person association: When customer contact information is entered in the contact management module, the system automatically associates the customer information; the management of internal contacts in the sales department, engineering department, on-site maintenance and technical department is automatically associated with customer information and project information. For example, engineering technicians can quickly view all the building projects they are responsible for through "Associate Projects".

[0066] Linking Project Documents with Client Information: When uploading documents such as requirements surveys, design documents, and engineering implementation documents in the project document management module, the system automatically links them to client and project information. Drawings, records, and other documents are automatically tagged with "Project Site + Application Service Type" for easy categorization and retrieval. During document operations, the system automatically records the uploader and time, and links them to client information, supporting the tracing of document modification records "by client + operator".

[0067] Customer information synchronization mechanism: When customer address, contact person's phone number, or other information changes, the system automatically triggers the information synchronization process: read the changed customer information > query all associated project IDs and application service IDs based on the customer ID > update the customer information of all associated projects > trigger the synchronization update of the project file management module; through this mechanism, "one change, multiple synchronizations" can be achieved, avoiding the problem of "maintenance personnel being unable to contact customers after their phone numbers change" in building service scenarios.

[0068] Permission association mechanism: The system automatically calculates and displays permissions associated with project files, customer information, and contacts; user permission management supports cross-project management, allowing different permission levels to be set for different projects; When synchronizing customer information changes, the following steps can be performed: The system administrator updates the customer's contact information in the customer information management module; The information association engine automatically identifies all items associated with this customer; The system automatically updates contact information for all projects involved; The project file management module synchronously updates the contact information for associated files; The system records a change log, including the time of the change, the person making the change, and the content of the change.

[0069] 3. Intelligent push system: Contract validity period management: Enter the contract validity period in the project information management module, and the system will automatically calculate the contract expiration time and set the expiration reminder threshold by default according to the dimensions such as "service type + customer level". VIP customers who provide long-term services will be reminded 30 days in advance by default. Message Template Settings: In the project information push management module, users can edit / add / delete message templates and set exclusive reminder content for different customer projects. For example, a template for industrial park customers can include a "Synchronous Renewal of Multi-Site Services in the Park" reminder. Templates support dynamic variable replacement, such as customer name, contract number, and expiration date. When generating a reminder, the system automatically replaces the variables with the actual values; for example: "[BIVALE Platform] Your project (Contract No.: contract id) will expire in {days} days. Please renew the contract in a timely manner."

[0070] Push notification settings: Users can set automatic triggering (on / off), push targets (select customer contacts, internal company contacts), and push schedule (X days in advance, Y days interval, repeat push). Different push rules can be set according to dimensions such as "service type + customer level". Multiple push methods are supported: in-app messages, WeChat, SMS, and email, ensuring timely message delivery. By introducing an intelligent push decision-making algorithm, the reminder strategy can be dynamically adjusted based on factors such as customer type, project importance, and contract amount.

[0071] Scheduled task execution: The system automatically triggers push notifications at specified times based on scheduled task settings; for example, 30 days before the contract expires, a WeChat and SMS reminder is sent to the customer's contact person; 7 days before the expiration, an in-system message reminder is sent to the sales department and on-site maintenance department; for high-value customers (contract amount ≥ 1 million), a "manual follow-up reminder" is added 3 days before the expiration and pushed to the account manager.

[0072] The client's project contract expires in 30 days. The following steps can be taken: The system calculates the expiration date based on the contract's validity period; The intelligent reminder decision tree algorithm determined that the project was a "high-importance" enterprise customer project; The system is set to remind you three times in advance: 30 days, 15 days, and 7 days. The system sends reminders to customer contacts via WeChat and SMS; The system sends reminders to contacts in the company's internal sales departments via in-system messaging.

[0073] 4. Cross-project access control: Role-based fine-grained access control: The system supports role management, allowing different permissions to be set for different roles, such as account managers, project managers, and technical engineers. Permissions can be refined to specific functional modules, such as customer information management, project information management, and contact management. Cross-project permission switching: Users can flexibly switch permissions between different projects without having to log in or re-authorize. When switching, the system automatically loads the project's exclusive functions; permissions are automatically associated with customer information, achieving intelligent matching of "customer-project-permission".

[0074] Permission Calculation and Display: The system automatically calculates and displays the user's permission level in each project. For example, user A has "edit" permission in project X and "view" permission in project B. It supports "batch permission configuration," which allows users to set permissions uniformly for multiple projects in the same region, improving management efficiency.

[0075] If a client needs to manage two projects simultaneously, the following steps can be taken: After a customer logs into the system, the system automatically loads their permissions and roles; The system calculates the permissions for the two items based on the permission role matrix; "Project A": This project is of high importance and has "read and write" permissions. "Project B": In the project importance section, the permission is "View"; When a customer switches projects in the system, the system automatically updates permissions; Customers can perform editing operations in project "A"; Customers can only view information in project "B".

[0076] 5. Intelligent query function: Multi-condition combined query: Users can perform queries through combinations of conditions such as contract number, project name, service site ID, customer category, contract validity period, and document category in the "Project Information Query Management" interface. The system automatically associates customer information, project document information, contact information, and application service status.

[0077] Supports jump-to-search: Search results can directly jump to the customer information management, project file management, and contact management interfaces. For example, if you search for contract number "CON2023001", you can click "Customer Information" in the results to view the customer details directly.

[0078] Information list display: Query results are displayed as an information list, including key information such as customer name, project name, contract number, contract validity period, and contact person. Sorting by field and exporting are supported.

[0079] The various embodiments of this application have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A project management system based on multi-dimensional information association, characterized in that, include: Information association engine, access control center, full-cycle information management module, customer project information query module, and customer project information push module; The full-cycle information management module is used to integrate customer basic information, project contract information, contact information and multi-format project files, and provides full-process management of information entry, storage, update and version control, and supports automatic synchronization and verification of information changes; The permission control center is used to establish a four-level permission control system of user-role-functional module-data scope. Through row-level data isolation and fine-grained configuration of module operation permissions, it enables secure access and flexible switching of data across projects and sites. The information association engine is used to build and maintain the association system of customers-projects-contacts-files. It adopts three technologies: primary keyword binding, association index mapping and semantic intelligent matching to achieve deep association and real-time synchronization of cross-dimensional data and support efficient processing of tens of millions of data volumes. The customer project information query module is used to receive multi-dimensional combined query requests, provide a retrieval method that combines precise query and fuzzy query, and realize one-click jump to query results and multi-dimensional data association display; The customer project information push module is used to automatically trigger and accurately deliver customized reminder messages based on project contract attributes and customer classification information through multiple push channels. Each module achieves collaborative operation through a distributed data interaction protocol, adapting to the multi-project management needs of cloud platform building integrated service scenarios.

2. The project management system based on multi-dimensional information association according to claim 1, characterized in that, The information association engine includes: The system includes a model management unit, a synchronization update unit, and a data verification unit. The association model management unit is used to build and maintain a four-dimensional association relationship of "customer-project-contact-file". It realizes data association through a triple association method of primary key, association index and semantic mapping. It establishes an association index table of project, contact and file through the unique identifier of customer, and then builds exclusive association fields between application service and project. The semantic mapping technology is based on TF-IDF algorithm and cosine similarity calculation. The synchronization update unit adopts a dual mechanism of triggered synchronization and timed verification. When any dimension information changes, it triggers the synchronous update of the associated data, and the synchronization scope covers the relevant records of all associated dimensions. The data verification unit periodically performs full data consistency verification, focusing on verifying the consistency between contact information and project files, and the matching of application service validity period and contract validity period, to ensure data accuracy.

3. The project management system based on multi-dimensional information association according to claim 1, characterized in that, The access control center includes: Permission configuration unit and access control unit; The permission configuration unit supports multiple role configurations such as super administrator, project administrator, and ordinary operator. It can be refined to specific operation permissions such as file viewing / editing / downloading, read-only / modification of customer information, and access to application service data. The data access scope can be further subdivided according to the region to which the project belongs and the type of application service. The access control unit establishes a permission mapping relationship based on user ID and project ID, and uses SQL statements to dynamically construct permission filtering conditions to achieve data isolation. It supports seamless switching between multiple authorized projects without requiring users to log in again, and the permission loading time is no more than 1 second.

4. The project management system based on multi-dimensional information association according to claim 1, characterized in that, The full-cycle information management module includes: Customer information management module and customer project document management module; The customer information management module is used to input and store basic customer information, project information, and contact information, and supports data verification. Basic customer information includes customer name, customer category, region, project address, customer number, and account configuration information. Project information includes contract number, contract validity period, contract status, application service association information, service status, and project file association information; application service association information supports multi-site service binding. Contact information includes customer contact information and internal contact information. Customer contact information includes the names, phone numbers, and email addresses of at least two groups of contacts; internal contact information is stored by department and supports contact priority settings, with push notifications sent in priority order. The customer project file management module supports uploading, adding, deleting, and downloading various file formats such as Word, Excel, PPT, PDF, drawings, and images. It enables precise association between files and projects and application services, and allows for traceability and management based on the modifier, file category, and upload time. It also features file version control functionality.

5. The project management system based on multi-dimensional information association according to claim 1, characterized in that: The customer project information query module supports combined retrieval of multiple query conditions, including contract number, project name, service site ID, customer category, contract validity period, and document category. It allows for any combination of 2-6 query conditions. We employ three optimization techniques to improve query response efficiency: caching popular query results in Redis, creating composite indexes on key fields, and loading query results in pages. The query results include basic customer information, project contract information, contact information, associated file information, and application service status. It supports one-click jump to the corresponding details page. The query list supports sorting by any field and Excel export function, exporting data content of different dimensions.

6. The project management system based on multi-dimensional information association according to claim 1, characterized in that, The customer project information push module includes: Push rule configuration unit, message template unit, and push execution unit; The push rule configuration unit allows for custom push rules based on dimensions such as project type, project importance, customer type, customer level, contract amount, and service type. It also allows for setting multi-level push strategies, including advance trigger time, repeated push interval, and expedited reminders. The message template unit provides multiple preset templates for renewal reminders, service changes, and maintenance notices. It also supports user-defined template content and allows the insertion of dynamic variables, drawings, attachments, and jump links. The push execution unit integrates four major push channels: in-site messages, WeChat, SMS, and email. It supports both batch push and single-point push modes, records push time, recipients, push status, and open rate, and performs secondary pushes for undelivered messages.

7. The project management system based on multi-dimensional information association according to claim 6, characterized in that: The customer project information push module has a built-in intelligent reminder decision tree model that dynamically adjusts the push strategy based on the multi-dimensional attributes of projects and customers. For enterprise clients, high-importance clients, important clients with contract amounts exceeding a certain amount, and long-term service clients, the frequency of push notifications is increased compared to ordinary clients, the number of days in advance for expedited reminders is increased, and a multi-level push strategy is set up with triggering X days in advance, repeating at Y-day intervals, and expedited reminders Z days before the due date, prioritizing WeChat and SMS push channels; For individual clients, projects of average importance, with contract amounts less than a certain amount, and for short-term services, set up two push notifications that are triggered X days in advance and repeated Y days apart, using SMS and in-site message push channels.

8. A project management method based on multi-dimensional information association, applied to the project management system based on multi-dimensional information association as described in any one of claims 1-7, characterized in that, include: The system retrieves basic customer information, project contract information, project-related documents, and contact information from the database to generate a unique customer ID. It then establishes a four-dimensional association model of customer-project-contact-file using primary keys, association indexes, and semantic mapping to link disparate data entities. Specifically, basic customer information includes the customer name, category, region, and address; project contract information includes contract number, validity period, service status, and customer and internal department contact information, automatically associated with the customer ID; and project-related documents are uploaded, generating file IDs that are then associated with the project ID and application service ID. When any dimension of information changes, the associated data is synchronously updated according to predefined association rules, covering all related items, contact records and file attributes; at the same time, full data verification is performed regularly to compare and repair inconsistencies, ensuring that multi-dimensional information is always consistent. Record all change operations in a log for auditing and traceability purposes; Access control and data isolation are based on a four-level access model of user-role-module-data, allowing for fine-grained access permission configuration. Users can seamlessly switch between different projects based on the list of authorized project IDs. Access filtering conditions are dynamically constructed using SQL to ensure that users can only access data in authorized projects. Searches can be performed using multiple conditions such as contract number, project name, service site ID, customer category, validity period, and file category. The query results are optimized using caching, indexing, and pagination techniques, presenting comprehensive information on customers, projects, contacts, and related files, and providing links to detailed information about the query results. Based on the project contract validity period, and combined with multiple dimensions such as customer level, project importance, contract amount, and service type, a reminder strategy is dynamically set. Projects to be reminded are automatically filtered through preset rules, and customized reminder content is pushed according to contact priority and preferred channels to ensure that no key nodes are missed. Based on the project contract validity period, and combined with multiple dimensions such as customer level, project importance, contract amount, and service type, a reminder strategy is dynamically set. Projects to be reminded are filtered by preset rules such as advance notice days, repetition frequency, and expedited thresholds. Customized reminder content is pushed according to contact priority and preferred channels to ensure that no key milestones are missed.

9. The project management method based on multi-dimensional information association according to claim 8, characterized in that, The establishment of the four-dimensional relationship model of customer-project-contact-file includes: Establish associated index records for projects, contacts, files, and application services, using the customer's unique identifier as the primary key; Through semantic intelligent matching technology, intelligent recognition and association of customer name aliases, project abbreviations, and file categories can be achieved; A database sharding and table partitioning strategy is adopted, with related data stored in separate databases based on the project's location and in separate tables based on the contract's validity period, ensuring efficient response to related queries.

10. The project management method based on multi-dimensional information association according to claim 8, characterized in that, The access control and data isolation include: The super administrator assigns roles to users and configures corresponding functional module operation permissions for each role. Specific data access scopes can be configured for each user, and can be further subdivided by project, region, and application service type; After a user logs into the system, the access control unit dynamically filters data based on permission mapping relationships, displaying only information within the user's authorized scope. When a user switches projects, the permission configuration for the corresponding project is automatically loaded.