Method for comprehensively displaying enterprise management information based on Web technology

Through the enterprise management information system based on Web technology, multi-source data is integrated in real time and three-dimensional interfaces are generated using WebGL technology, the problems of low data integration and display efficiency, insufficient user personalized adjustments and permission management in the existing system are solved, and efficient information display and data security.

CN118917562AInactive Publication Date: 2024-11-08KAIHUI TECH CO LTD

Patent Information

Application Number
CN202411413442.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-11
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Due to the dispersibility and complexity of data, existing enterprise management information systems are difficult to achieve real-time data integration and dynamic display, which cannot meet the enterprise's efficient decision-making needs. At the same time, there is a lack of user personalized adjustments and sensitive data permission management, resulting in data security risks.

Method used

Through a method based on Web technology, data from multiple business systems can be obtained in real time, format standardization and abnormal detection, integrated into a unified database, and a three-dimensional visual interface is generated using WebGL technology to support user interaction and permission control, and dynamically adjust data display. Role-based access management.

Benefits of technology

Realize real-time dynamic display of enterprise management information, improve data processing and display efficiency, ensure user experience and data security, and avoid the risks of overprivileged access and information leakage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118917562A_ABST
    Figure CN118917562A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of enterprise information management, in particular to a method for comprehensively displaying enterprise management information based on a Web technology, which comprises the following steps of: S1, acquiring the enterprise management information from a plurality of business systems in real time; s2, performing format standardization and compression processing on the data acquired in the S1; s3, integrating the data processed in the step S2 into a unified database; s4, identifying and classifying preset events, and sorting the identified events according to priorities; s5, generating a three-dimensional visual interface through a WebGL technology, wherein the three-dimensional visual interface is used for displaying enterprise management information; s6, dynamically adjusting the layout and content of data display; and S7, setting access permissions for different users. According to the method, the enterprise multi-source management information is dynamically displayed in real time, the personalized interaction interface is provided, and the access control rule based on the role is implemented, so that the data processing efficiency and the user experience are improved, and the security of sensitive data and the compliance of the system are guaranteed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of enterprise information management, and in particular to a method for realizing comprehensive display of enterprise management information by using Web-based technology. Background Art

[0002] With the rapid development of enterprise informatization, enterprise management systems have played an increasingly important role in enterprise operations. These systems usually cover multiple business areas, such as finance, customer relationship management, supply chain, human resource management, etc., with the aim of improving enterprise operational efficiency, optimizing resource allocation and supporting decision-making. However, most of the existing enterprise management information systems adopt a decentralized structure, and data from different departments are usually stored in their own independent systems, lacking a unified means of data integration and display. Due to the dispersion and complexity of data, enterprises often face huge challenges in obtaining real-time comprehensive information to support efficient decision-making. In addition, with the increase in the amount of data, how to display these multi-dimensional data in a clear and intuitive way to help enterprise managers quickly grasp key information is also one of the problems that need to be solved in the current enterprise management system.

[0003] In the existing technology, although some systems have introduced Web technology for information display, there are still several difficult problems: first, the data integration efficiency between different business systems is low, resulting in information lag and the inability to achieve real-time update and dynamic display of data; second, the system lacks a dynamic adjustment mechanism for user personalized needs, and users cannot customize data display according to their own usage habits; finally, the permission management mechanism for sensitive data is imperfect, resulting in potential risks to enterprises in terms of data security. Therefore, there is an urgent need for a method for comprehensive display of enterprise management information that can realize real-time dynamic display of enterprise multi-source management data. Summary of the invention

[0004] Based on the above objectives, the present invention provides a method for realizing comprehensive display of enterprise management information using Web-based technology.

[0005] The method for realizing comprehensive display of enterprise management information using Web-based technology includes the following steps:

[0006] S1: Obtain enterprise management information in real time from multiple business systems through data interfaces, including finance, customer relationship management, supply chain and human resource management;

[0007] S2: Standardize and compress the data collected by S1, and identify and correct anomalies in the data through anomaly detection algorithms;

[0008] S3: Integrate the data processed by S2 into a unified database in chronological order and in an incremental manner;

[0009] S4: Performs real-time analysis of data in the S3 database based on preset rules and event detection algorithms to identify and classify preset events and sort the identified events by priority;

[0010] S5: Based on the classification and priority sorting results in S4, a three-dimensional visualization interface is generated through WebGL technology to display enterprise management information and support manual screening and interactive operations by users;

[0011] S6: Based on the user's operation behavior in S5, collect feedback and analyze user preferences, and then dynamically adjust the layout and content of data display;

[0012] S7: Set access permissions for different users and limit user access to sensitive data based on role control rules.

[0013] Optionally, the S1 specifically includes:

[0014] S11: Based on the REST API protocol, a unified data transmission format is adopted, including JSON or XML, to build a standardized interface for data request and response between various business systems;

[0015] S12: Use the OAuth 2.0 protocol to authenticate the business system, generate authorization tokens to ensure secure data access connections, and regularly refresh authorization credentials to prevent credential expiration;

[0016] S13: Implement an event-based trigger mechanism in the data interface, and predefine data change conditions for each business system through the trigger mechanism, including adding, updating or deleting operations in the database; when the data in the business system changes, the trigger mechanism will automatically capture the change event, and send the event to the interface through the message queue technology;

[0017] S14: During the data transmission process, if data transmission fails or an error occurs, the unsuccessful data will be resent and troubleshooting will be performed based on the error log.

[0018] Optionally, the S2 specifically includes:

[0019] S21: Standardize the format of data collected from multiple business systems, use ETL technology to convert the data output by each system into a unified format, and use JSON as the standard data format to ensure the consistency of data structure;

[0020] S22: After completing the format standardization, the data is compressed using the Gzip compression algorithm;

[0021] S23: For the formatted and compressed data, a rule-based anomaly detection algorithm is used to perform data verification, specifically including data range check and integrity check;

[0022] S24: When abnormal data is detected in S23, an abnormal correction algorithm is used to correct it. Specifically, by learning from historical data, potential correct values ​​are predicted and replaced and corrected. At the same time, the corrected data is marked and recorded in a log file.

[0023] Optionally, the S24 specifically includes:

[0024] S241: Building a prediction model based on historical data, wherein the prediction model analyzes the trends and rules of historical data and establishes relationships between variables, thereby identifying abnormal situations in current data;

[0025] S242: When a certain data is identified as abnormal, the prediction model constructed in S241 is used to calculate the correct value of the abnormal data according to the pattern and relationship of the historical data, and the original abnormal data is replaced with the predicted correct value;

[0026] S243: After replacing the modified data, a mark is added to each modified data to indicate that the data has been modified; the unmodified data retains the default mark;

[0027] S244: Record each correction operation, including original data, corrected data after replacement, and correction time information, and all records are stored in a log file.

[0028] Optionally, the S3 specifically includes:

[0029] S31: After S2 is processed, add a timestamp field to each data record to ensure that all data has a clear time order;

[0030] S32: Packing in batches according to timestamps to generate incremental data packets;

[0031] S33: Before the generated incremental data packet is transmitted to the database, a consistency check is performed on it to ensure that all records in the data packet have a continuous timestamp sequence and there is no duplication or omission;

[0032] S34: writing the verified incremental data packets one by one into a unified database in the order of timestamps, wherein the database adopts a time series storage structure, wherein each record is indexed according to the timestamp, so that the data can be efficiently stored and queried in time order;

[0033] S35: After the incremental data is written into the database, confirmation information of successful writing is automatically generated and recorded in a log file, wherein the log file includes the writing time range, data volume and writing status.

[0034] Optionally, the S4 specifically includes:

[0035] S41: defining a set of preset rules according to enterprise management requirements, wherein the rule set includes event triggering conditions, thresholds, time windows, and predetermined indicators, and each rule in the rule set is marked with a unique identifier;

[0036] S42: Based on a preset rule set, an event detection algorithm is applied to identify events that meet the rule conditions from the incremental data in S3, wherein the event detection algorithm performs real-time analysis on the time series data based on a sliding time window to identify abnormal fluctuations or predetermined patterns in the data;

[0037] S43: Classify the detected events according to the type of rules and trigger conditions, the event classification categories include emergency events, warning events and regular monitoring events, and each event is marked according to its corresponding rule type;

[0038] S44: Sort the detected events according to a predefined priority sorting algorithm, wherein the priority sorting algorithm is calculated based on factors of urgency, impact scope, and potential risk of the events;

[0039] S45: Continuously monitor the data stream and adjust the event priority list in real time according to the new events detected. When a new high-priority event is detected, the priority order of the existing events is automatically adjusted.

[0040] Optionally, the S44 specifically includes:

[0041] S441: Assign three influencing factors to each incident, including urgency, scope of impact, and potential risk. Each factor is weighted according to preset criteria to measure its impact on the incident priority.

[0042] S442: Calculate a priority score for each event based on the weights of the above three factors, and perform weighted processing on the urgency, scope of impact and potential risks according to the weights to calculate the total score of each event;

[0043] S443: Dynamically adjust the weights of urgency, impact scope and potential risks according to different business scenarios or event categories;

[0044] S444: Based on the priority score, all detected events are sorted by score. Events with higher scores are processed first. The entire sorting process is dynamic. When a new high-priority event is detected, the sorting order of the events is automatically adjusted.

[0045] Optionally, the S5 specifically includes:

[0046] S51: According to the classification and priority sorting results in S4, different categories of events and information are mapped to the corresponding three-dimensional coordinate space, and the event data is converted into three-dimensional objects through the WebGL rendering engine. Each object is given a different color, shape and size according to its classification. Events with higher priority are displayed in a more eye-catching way in the visualization interface;

[0047] S52: Generate a 3D visualization interface using WebGL technology. The layout of the 3D space is designed based on the classification and priority of events. High-priority events are placed at the core of the interface, allowing users to rotate, scale, and move 3D objects through mouse or touch operations to obtain different perspectives.

[0048] S53: monitors data changes from the S3 database, and dynamically updates the display status of the three-dimensional object according to the new priority sorting results. Specifically, when a high-priority event is detected, the three-dimensional interface will automatically refresh the display and insert the new high-priority event into the visualization interface;

[0049] S54: The visualization interface also supports users to manually filter events and data, allowing users to filter the displayed content by category, time range or priority through the filtering tools on the interface.

[0050] Optionally, the S6 specifically includes:

[0051] S61: When the user interacts with the 3D visualization interface in S5, the user's operation behavior is recorded in real time, including clicks, filtering, zooming, rotation, and data filtering conditions;

[0052] S62: Analyze the user preference using the collected user operation behavior data using a behavior analysis algorithm, wherein the behavior analysis algorithm calculates the user's preference weight according to the user's operation frequency, operation duration, event category of interest, and screening conditions;

[0053] S63: Based on the user preference analysis result, analyzing the user preference weight, determining the category of data or events that need to be displayed first;

[0054] S64: Dynamically adjust the data display content based on the preferences analyzed from the user's operation behavior, and prioritize loading data of related categories based on the user's filtering conditions or focus, thereby reducing unnecessary data loading and display.

[0055] Optionally, the S7 specifically includes:

[0056] S71: Set a unique identity for each user, and verify the user's identity through the authentication mechanism when the user logs in. When registering or allocating an account, each user will be assigned different roles, including administrators, financial personnel, and ordinary users;

[0057] S72: defining permission sets for different roles according to the management requirements of the enterprise, with each role being associated with a predetermined set of data access permissions, including permissions to read, write, modify or delete predetermined data;

[0058] S73: Classify data in enterprise management information and mark sensitive data, including financial statements, customer information and contracts; each piece of data is graded according to its sensitivity level and marked as public, restricted or confidential;

[0059] S74: Based on the user's role and permission set, the role-based access control rules are applied. When a user requests to access a certain data, it is first checked whether the user's role has the corresponding permission; if the user's permission level is not higher than the sensitivity level of the data, the access request is denied;

[0060] S75: Dynamically adjust roles and permissions based on changes in user responsibilities. When a user's position changes or job responsibilities are adjusted, the system administrator can modify their role assignment to ensure that they have data access permissions consistent with their new responsibilities.

[0061] Beneficial effects of the present invention:

[0062] The present invention realizes the real-time dynamic display of enterprise management information by integrating data from multiple business systems and adopting 3D visualization technology based on WebGL. Compared with the existing technology, it can process and display multi-source data more efficiently. Users can quickly understand the operating status of the enterprise through an intuitive 3D interface and respond to key events in a timely manner according to priority. In addition, the present invention supports users to dynamically adjust the data display layout through personalized screening and interactive operations, which greatly improves the user experience and the efficiency of information acquisition.

[0063] The present invention effectively protects the security of sensitive data through role-based access control, ensures that different users can only access data related to their responsibilities, avoids the risk of unauthorized access and information leakage, and combines real-time data update and permission audit mechanism to not only improve the intelligence and automation level of enterprise management, but also ensure the security and compliance of system operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only for the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0065] Figure 1 A schematic diagram of a method for comprehensively displaying enterprise management information according to an embodiment of the present invention;

[0066] Figure 2 Schematic diagram of a method for applying an anomaly correction algorithm according to an embodiment of the present invention. DETAILED DESCRIPTION

[0067] The present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. At the same time, it is explained here that in order to make the embodiments more detailed, the following embodiments are the best and preferred embodiments, and those skilled in the art may also adopt other alternatives to implement some known technologies; and the accompanying drawings are only for more specific description of the embodiments, and are not intended to specifically limit the present invention.

[0068] It should be noted that the references to "one embodiment", "embodiment", "exemplary embodiments", "some embodiments" and the like in the specification indicate that the embodiments described may include specific features, structures or characteristics, but not every embodiment may include the specific features, structures or characteristics. In addition, when a specific feature, structure or characteristic is described in conjunction with an embodiment, it should be within the knowledge of a person skilled in the art to implement such feature, structure or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0069] In general, a term can be understood, at least in part, from its use in context. For example, depending, at least in part, on the context, the term "one or more" as used herein can be used to describe any feature, structure, or characteristic in the singular sense, or can be used to describe a combination of features, structures, or characteristics in the plural sense. Additionally, the term "based on" can be understood as not necessarily intended to convey an exclusive set of factors, but can instead, depending, at least in part, on the context, allow for the presence of other factors that are not necessarily explicitly described.

[0070] like Figure 1-Figure 2 As shown, the method for realizing comprehensive display of enterprise management information using Web-based technology includes the following steps:

[0071] S1: Through data interfaces, enterprise management information is obtained in real time from multiple business systems, including finance, customer relationship management, supply chain and human resource management, to ensure data continuity and real-time performance;

[0072] S2: Standardize and compress the data collected by S1, and identify and correct anomalies in the data through anomaly detection algorithms to ensure data consistency and reliability;

[0073] S3: Integrate the data processed by S2 into a unified database in chronological order in an incremental manner, and use a time series storage structure to support fast data writing, reading, and historical data tracing;

[0074] S4: Performs real-time analysis of data in the S3 database based on preset rules and event detection algorithms to identify and classify preset events, and sorts the identified events by priority to provide core information to support subsequent presentation;

[0075] S5: Based on the classification and priority sorting results in S4, a three-dimensional visualization interface is generated through WebGL technology to display enterprise management information, and supports manual screening and interactive operations by users to achieve intuitive and dynamic display of information;

[0076] S6: Based on the user's operation behavior in S5, collect feedback and analyze user preferences, and then dynamically adjust the layout and content of data display to optimize visualization effects and user experience;

[0077] S7: Set access permissions for different users and limit user access to sensitive data based on role control rules to ensure data security and compliance.

[0078] S1 specifically includes:

[0079] S11: Based on the REST API protocol, a unified data transmission format is adopted, including JSON or XML, to build a standardized interface for data request and response between various business systems. The interface supports asynchronous requests to ensure that the response delay between systems is reduced during the data transmission process;

[0080] S12: Use the OAuth 2.0 protocol to authenticate the business system, generate authorization tokens to ensure secure data access connections, and regularly refresh authorization credentials to prevent credential expiration. All data requests are encrypted and transmitted through the API interface to prevent data from being intercepted or tampered with in the network.

[0081] S13: Implement an event-based trigger mechanism in the data interface. The trigger mechanism predefines data change conditions for each business system, including adding, updating or deleting operations in the database. When data in the business system changes, the trigger mechanism automatically captures the change event and sends the event to the interface through message queue technology (such as Kafka or RabbitMQ). The interface then starts the data synchronization operation to ensure that the data is updated in real time when it changes.

[0082] S14: During the data transmission process, if data transmission fails or an error occurs, the unsuccessful data will be resent, and troubleshooting will be performed based on the error log to ensure the stability and continuity of data synchronization; through the above steps, S1 can ensure real-time data collection, secure access, and rapid response to change events in multiple business systems, ensuring the accuracy and timeliness of management information.

[0083] S2 specifically includes:

[0084] S21: Standardize the format of data collected from multiple business systems. Use ETL (extraction, transformation, loading) technology to convert the data output by each system into a unified format. Use JSON (JavaScript Object Notation) as the standard data format to ensure the consistency of the data structure. During the standardization process, uniformly convert field names, data types, timestamps, etc. to avoid data incompatibility issues across systems.

[0085] S22: After the format is standardized, the data is compressed using the Gzip compression algorithm. This algorithm reduces the size of the transmitted data and improves transmission efficiency. It is particularly suitable for processing large-scale data sets. During the compression process, the streaming compression mode is used to ensure that the data is transmitted with minimal bandwidth usage.

[0086] S23: For the formatted and compressed data, a rule-based anomaly detection algorithm is used to perform data verification, including data range check and integrity check. First, the content of the field is checked by defining a reasonable value range and legal format. Second, the data integrity is verified by a hash check code to ensure that the data is not damaged or lost during the collection process.

[0087] S24: When abnormal data is detected in S23, an abnormal correction algorithm is used to correct it. Specifically, by learning from historical data, potential correct values ​​are predicted and replaced and corrected. At the same time, the corrected data is marked and recorded in the log file for subsequent review and verification.

[0088] The abnormal correction algorithm used in S24 specifically includes:

[0089] S241: Building a prediction model based on historical data. The prediction model analyzes the trends and patterns of historical data and establishes relationships between variables, thereby identifying anomalies in current data. By continuously training the model, it is able to predict anomalies in current data based on past data patterns.

[0090] S242: When a certain data is identified as abnormal, the prediction model constructed in S241 is used to calculate the correct value of the abnormal data according to the pattern and relationship of the historical data, and the original abnormal data is replaced with the predicted correct value. This replacement operation ensures the continuity and consistency of the data flow;

[0091] S243: After replacing the corrected data, a mark is added to each corrected data to indicate that the data has been modified; the uncorrected data retains the default mark so as to distinguish the original data from the corrected data in subsequent operations;

[0092] S244: Record each correction operation, including the original data, the corrected data after replacement, and the time information of the correction. All records are stored in a log file for subsequent review and verification of the accuracy of the correction. The above steps realize anomaly correction through the historical data learning model, and the abnormal data is predicted and replaced in combination with the algorithm. At the same time, the corrected data is marked and recorded in detail to ensure the integrity and traceability of the data.

[0093] The steps for correction using the anomaly correction algorithm are as follows:

[0094] Historical data learning model construction: Assume that the input data set is ,in, Represents the historical data Input values, Represents the corresponding output result; the linear regression model optimizes the parameters To predict abnormal data; predict value The calculation is done by the following formula: ,in, represents the predicted output value, is the bias parameter, is the regression coefficient, is the characteristic value of the input data set; preset minimization error function To optimize these parameters, the function The expression is: ,in, is the sample size, For the Prediction values, For the This process enables the model to make more accurate predictions when encountering abnormal data;

[0095] Outlier prediction and replacement: When a data When detected as an abnormality, the model constructed in S241 is used to predict the abnormal value, and the model parameters The calculated predicted value is the potential correct value of the abnormal data, which is calculated by the following formula: ,in, is the replacement value for abnormal data, are model parameters, is the characteristic value of historical data; Replace with the predicted correct value ;

[0096] Data labeling: Corrected data A tag field is added , used to distinguish the corrected data from the original data; specifically for the corrected data, the tag value , while the uncorrected data marker value ; The final data storage format is ,in, is the original outlier, is the corrected value, It is a flag value, indicating whether the data has been modified.

[0097] S3 specifically includes:

[0098] S31: After S2 is processed, a timestamp field is added to each data record to ensure that all data has a clear time sequence. The timestamp is generated based on Coordinated Universal Time (UTC) to ensure the consistency and accuracy of time when data is integrated across systems;

[0099] S32: Packing in batches according to timestamps to generate incremental data packets; the incremental data packets only contain new or updated data compared to the last transmission, avoiding transmission of redundant data and improving integration efficiency;

[0100] S33: before the generated incremental data packet is transmitted to the database, a consistency check is performed on it to ensure that all records in the data packet have a continuous timestamp sequence without duplication or omission, and the specific check is verified by comparing the last timestamp of the previous incremental transmission with the timestamp of the first data item of the current incremental data packet;

[0101] S34: writing the verified incremental data packets one by one into a unified database in the order of timestamps. The database adopts a time series storage structure, in which each record is indexed according to the timestamp, so that the data can be efficiently stored and queried in time order;

[0102] S35: After the incremental data is written to the database, confirmation information of successful writing is automatically generated and recorded in the log. The log file includes the writing time range, data volume and writing status to ensure that all data integration operations can be reviewed and verified. The above steps ensure that the data processed by S2 can be efficiently and accurately integrated into a unified database in an incremental manner and in chronological order, ensuring the continuity, consistency and traceability of the data.

[0103] S4 specifically includes:

[0104] S41: Define a set of preset rules according to enterprise management requirements. The rule set includes event trigger conditions, thresholds, time windows, and predetermined indicators. Each rule in the rule set is marked with a unique identifier to ensure accuracy in subsequent processing.

[0105] The rule set includes but is not limited to the following situations:

[0106] Financial fluctuation warning: When revenue, profit or cash flow fluctuates beyond a preset threshold (for example, a drop of more than 5% or an increase of more than 10%) within a specified time window, a financial warning event is triggered;

[0107] Inventory level warning: when the inventory level drops to the preset minimum safety stock line, a stock replenishment event is triggered. The rules can include inventory threshold settings for different product categories.

[0108] Customer churn warning: When a customer's purchase frequency or transaction amount drops continuously over a period of time (for example, a drop of more than 30% within three months), a customer churn warning event is triggered;

[0109] Production equipment anomaly detection: when the operating status data (such as temperature, vibration frequency, etc.) of the production equipment exceeds the set safety range, the equipment maintenance or shutdown warning event is triggered;

[0110] Supply chain disruption warning: when suppliers fail to deliver on time or raw materials are insufficient, a supply chain disruption event is triggered so that timely response measures can be taken;

[0111] Compliance risk monitoring: When contract terms, policy changes or other events that may cause legal risks are detected, compliance risk monitoring events are triggered.

[0112] S42: Based on the preset rule set, the event detection algorithm is applied to identify events that meet the rule conditions from the incremental data in S3. The event detection algorithm is based on a sliding time window to perform real-time analysis on the time series data to identify abnormal fluctuations or predetermined patterns in the data. During the operation, events that meet the rule conditions are detected in real time and immediately marked as "detected";

[0113] S43: Classify and process the detected events according to the rule types and trigger conditions. The event classification categories include emergency events, warning events, and regular monitoring events. Each event is marked according to its corresponding rule type for subsequent priority sorting and processing;

[0114] S44: Sort the detected events according to a predefined priority sorting algorithm. The priority sorting algorithm is calculated based on factors such as the urgency, impact scope, and potential risk of the event. For example, an event with a high urgency and a large impact scope will be given a higher priority. The sorting algorithm scores each event according to a weight value. An event with a higher score has a higher priority.

[0115] S45: Continuously monitor the data stream and adjust the event priority list in real time based on the new events detected. When a new high-priority event is detected, automatically adjust the priority order of existing events to ensure that high-priority events can be processed and responded to first. The above steps realize real-time analysis of data in the S3 database, accurate detection and classification of events, and ensure that the most important events are responded to and processed in a timely manner through the priority sorting algorithm.

[0116] S44 specifically includes:

[0117] S441: Assign three influencing factors to each event, including urgency, impact scope, and potential risk. Each factor is weighted according to the preset standard to measure its impact on the event priority. The urgency is used to reflect the urgency of event handling, the impact scope indicates the breadth of the event's coverage of the business, and the potential risk indicates the potential harm caused by the event.

[0118] S442: Calculate a priority score for each event based on the weights of the above three factors, and perform weighted processing on the urgency, impact scope and potential risk according to the weights to calculate the total score of each event. The higher the score, the higher the priority. The system will determine the order of handling the events based on this score.

[0119] S443: Dynamically adjust the weights of urgency, impact, and potential risks based on different business scenarios or event categories. For example, in customer-related events, the weight of urgency may be increased; while in production-related events, the weight of impact may be higher, ensuring that business-critical issues are handled with priority;

[0120] S444: Based on the priority score, all detected events are sorted by score. Events with higher scores are processed first. The entire sorting process is dynamic. When a new high-priority event is detected, the sorting order of the events is automatically adjusted to ensure that the most important events receive a timely response. Through these steps, the priority can be reasonably calculated based on the urgency, scope of impact and potential risks of the event, and high-priority events can be processed first through sorting.

[0121] The steps to sort the detected events are as follows:

[0122] Setting of event weight factors: Define three main influencing factors for each event, including urgency Scope of influence and potential risks , each factor is assigned a corresponding weight coefficient according to the preset rules , , , these weights are used to measure the impact of each factor on the event priority, where Indicates the urgency of the event, with higher values ​​indicating higher urgency; Indicates the business scope affected by the event. A larger value indicates a wider impact scope. Indicates the potential risk brought by the event. The higher the value, the greater the risk.

[0123] Priority score calculation: Calculate the priority score of each event based on the weight factor , the calculation formula of priority score is as follows: ,in, Rate the priority of the incident, , , is the weight coefficient of each factor, and the value range can be adjusted according to actual needs. , , They are the specific values ​​of urgency, impact scope and potential risk. Each event is based on its specific , and The corresponding priority score is obtained by calculation ,The higher score indicates a higher priority of the event;

[0124] Prioritization: Score each event based on its priority The detected events are sorted in descending order. Events with higher scores have higher priorities, and the system will process these events first. The sorting results will be updated in real time to ensure that newly detected high-priority events can be immediately inserted into the front of the priority queue.

[0125] S5 specifically includes:

[0126] S51: According to the classification and priority sorting results in S4, different categories of events and information are mapped to the corresponding three-dimensional coordinate space, and the event data is converted into three-dimensional objects through the WebGL rendering engine. Each object is given a different color, shape and size according to its classification. Events with higher priority are displayed in a more eye-catching way in the visualization interface;

[0127] S52: Generate a 3D visualization interface using WebGL technology. The layout of the 3D space is designed based on the classification and priority of events. High-priority events are placed at the core of the interface, allowing users to rotate, scale, and move 3D objects through mouse or touch operations to obtain different perspectives. The system uses an automatic layout algorithm to display various events in an orderly manner in the 3D space without overlap or confusion.

[0128] S53: monitors data changes from the S3 database, and dynamically updates the display status of the three-dimensional object according to the new priority sorting results. Specifically, when a high-priority event is detected, the three-dimensional interface will automatically refresh the display and insert the new high-priority event into the visualization interface;

[0129] S54: The visualization interface also supports users to manually filter events and data, allowing users to filter the displayed content by category, time range or priority through the filtering tools on the interface. For example, users can choose to only view high-priority events within a specific time period. The interface also supports interactive operations. Users can click on three-dimensional objects to view detailed event information, including the triggering cause of the event, processing status, etc. The above steps realize the generation of a three-dimensional visualization interface based on WebGL technology, displaying enterprise management information and supporting users' manual filtering and interactive operations, ensuring dynamic visualization of data and optimization of user experience.

[0130] S6 specifically includes:

[0131] S61: When the user interacts with the 3D visualization interface in S5, the user's operation behavior is recorded in real time, including clicks, filtering, zooming, rotation and data filtering conditions. Each operation behavior is accompanied by a timestamp and operation object information to ensure that the user's interaction details can be accurately captured;

[0132] S62: Analyze user preferences using a behavior analysis algorithm based on the collected user operation behavior data. The behavior analysis algorithm calculates the user's preference weight based on the user's operation frequency, operation duration, event category of interest, and screening conditions. For example, if a user frequently clicks or screens a certain type of event, the system regards this category as the user's preference category and increases its preference weight.

[0133] S63: Based on the user preference analysis result, the user preference weight is analyzed to determine the categories of data or events that need to be displayed first. For example, for event categories that users pay more attention to, the system will dynamically adjust their display positions, place them in a prominent position on the interface or expand their display range to ensure that users can quickly access the data of interest;

[0134] S64: According to the preferences analyzed from the user's operation behavior, the data display content is dynamically adjusted. According to the user's filtering conditions or concerns, the data of related categories is loaded first, and unnecessary data loading and display are reduced to improve the system response speed and user experience. For example, if the user often filters events within a specific time period, the system will automatically load and display the data of this time period first. The above steps realize the collection and analysis of feedback based on user operation behavior, and dynamically adjust the layout and content of data display to ensure that users get the best interactive experience and efficient data display in interface operations.

[0135] S7 specifically includes:

[0136] S71: Set a unique identity for each user, and verify the user's identity through an authentication mechanism (such as OAuth2.0 or multi-factor authentication) when the user logs in. Each user will be assigned different roles when registering or assigning an account, including administrator, financial personnel, and ordinary user;

[0137] S72: Define permission sets for different roles based on the management needs of the enterprise. Each role is associated with a predetermined set of data access permissions, including the permission to read, write, modify or delete predetermined data. The permission allocation within the system follows the principle of least privilege to ensure that users can only access the minimum data required for their roles. For example, financial personnel can only view sensitive data related to finance and cannot access confidential data of other departments.

[0138] S73: Classify data in enterprise management information and mark sensitive data, including financial statements, customer information and contracts; each piece of data is graded according to its sensitivity level and marked as public, restricted or confidential to ensure hierarchical management of access rights;

[0139] S74: Based on the user's role and permission set, role-based access control (RBAC) rules are applied. When a user requests to access a certain data, it is first checked whether the user's role has the corresponding permission; if the user's permission level is not higher than the sensitivity level of the data, the access request is denied;

[0140] S75: Dynamically adjust roles and permissions based on changes in user responsibilities. When a user's position changes or job responsibilities are adjusted, the system administrator can modify their role assignment to ensure that they have data access permissions consistent with their new responsibilities. In addition, the system will regularly generate permission usage reports to audit user access behavior and detect whether there is unauthorized access or abuse of permissions. The above steps ensure that precise access permissions are set for different users through role-based access control rules, preventing unauthorized users from accessing sensitive data and ensuring the security and compliance of enterprise management information.

[0141] The present invention covers any substitution, modification, equivalent method and scheme made on the essence and scope of the present invention. In order to make the public have a thorough understanding of the present invention, specific details are described in detail in the following preferred embodiments of the present invention, but those skilled in the art can fully understand the present invention without the description of these details. In addition, in order to avoid unnecessary confusion about the essence of the present invention, well-known methods, processes, procedures, components and circuits are not described in detail.

[0142] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for realizing comprehensive display of enterprise management information using Web-based technology, characterized in that: The following steps are involved: S1: Obtain enterprise management information in real time from multiple business systems through data interfaces, including finance, customer relationship management, supply chain and human resource management; S2: Standardize and compress the data collected by S1, and identify and correct anomalies in the data through anomaly detection algorithms; S3: Integrate the data processed by S2 into a unified database in chronological order and in an incremental manner; S4: Performs real-time analysis of data in the S3 database based on preset rules and event detection algorithms to identify and classify preset events and sort the identified events by priority; S5: Based on the classification and priority sorting results in S4, a three-dimensional visualization interface is generated through WebGL technology to display enterprise management information and support manual screening and interactive operations by users; S6: Based on the user's operation behavior in S5, collect feedback and analyze user preferences, and then dynamically adjust the layout and content of data display; S7: Set access permissions for different users and limit user access to sensitive data based on role control rules.

2. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 1, characterized in that: The S1 specifically includes: S11: Based on the REST API protocol, a unified data transmission format is adopted, including JSON or XML, to build a standardized interface for data request and response between various business systems; S12: Use the OAuth 2.0 protocol to authenticate the business system, generate authorization tokens to ensure secure data access connections, and regularly refresh authorization credentials to prevent credential expiration; S13: Implement an event-based trigger mechanism in the data interface, and predefine data change conditions for each business system through the trigger mechanism, including adding, updating or deleting operations in the database; when the data in the business system changes, the trigger mechanism will automatically capture the change event, and send the event to the interface through the message queue technology; S14: During the data transmission process, if data transmission fails or an error occurs, the unsuccessful data will be resent and troubleshooting will be performed based on the error log.

3. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 1, characterized in that: The S2 specifically includes: S21: Standardize the format of data collected from multiple business systems, use ETL technology to convert the data output by each system into a unified format, and use JSON as the standard data format to ensure the consistency of data structure; S22: After completing the format standardization, the data is compressed using the Gzip compression algorithm; S23: For the formatted and compressed data, a rule-based anomaly detection algorithm is used to perform data verification, specifically including data range check and integrity check; S24: When abnormal data is detected in S23, an abnormal correction algorithm is used to correct it. Specifically, by learning from historical data, potential correct values ​​are predicted and replaced and corrected. At the same time, the corrected data is marked and recorded in a log file.

4. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 3, characterized in that: The S24 specifically includes: S241: Building a prediction model based on historical data, wherein the prediction model analyzes the trends and rules of historical data and establishes relationships between variables, thereby identifying abnormal situations in current data; S242: When a certain data is identified as abnormal, the prediction model constructed in S241 is used to calculate the correct value of the abnormal data according to the pattern and relationship of the historical data, and the original abnormal data is replaced with the predicted correct value; S243: After replacing the modified data, a mark is added to each modified data to indicate that the data has been modified; the unmodified data retains the default mark; S244: Record each correction operation, including original data, replaced correction data, and correction time information, and all records are stored in a log file.

5. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 1, characterized in that: The S3 specifically includes: S31: After S2 is processed, add a timestamp field to each data record to ensure that all data has a clear time order; S32: Packing in batches according to timestamps to generate incremental data packets; S33: before the generated incremental data packet is transmitted to the database, a consistency check is performed on it to ensure that all records in the data packet have a continuous timestamp sequence and there is no duplication or omission; S34: writing the verified incremental data packets one by one into a unified database in the order of timestamps, wherein the database adopts a time series storage structure, wherein each record is indexed according to the timestamp, so that the data can be efficiently stored and queried in time order; S35: After the incremental data is written into the database, confirmation information of successful writing is automatically generated and recorded in a log file, wherein the log file includes the writing time range, data volume and writing status.

6. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 1, characterized in that: The S4 specifically includes: S41: defining a set of preset rules according to enterprise management requirements, wherein the rule set includes event triggering conditions, thresholds, time windows, and predetermined indicators, and each rule in the rule set is marked with a unique identifier; S42: Based on a preset rule set, an event detection algorithm is applied to identify events that meet the rule conditions from the incremental data in S3, wherein the event detection algorithm performs real-time analysis on the time series data based on a sliding time window to identify abnormal fluctuations or predetermined patterns in the data; S43: Classify the detected events according to the type of rules and trigger conditions, the event classification categories include emergency events, warning events and regular monitoring events, and each event is marked according to its corresponding rule type; S44: Sort the detected events according to a predefined priority sorting algorithm, wherein the priority sorting algorithm is calculated based on factors of urgency, impact scope, and potential risk of the events; S45: Continuously monitor the data stream and adjust the event priority list in real time according to the new events detected. When a new high-priority event is detected, the priority order of the existing events is automatically adjusted.

7. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 6, characterized in that: The S44 specifically includes: S441: Assign three influencing factors to each incident, including urgency, scope of impact, and potential risk. Each factor is weighted according to preset criteria to measure its impact on the incident priority. S442: Calculate a priority score for each event based on the weights of the above three factors, and perform weighted processing on the urgency, scope of impact and potential risks according to the weights to calculate the total score of each event; S443: Dynamically adjust the weights of urgency, impact scope and potential risks according to different business scenarios or event categories; S444: Based on the priority score, all detected events are sorted by score. Events with higher scores are processed first. The entire sorting process is dynamic. When a new high-priority event is detected, the sorting order of the events is automatically adjusted.

8. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 1, characterized in that: The S5 specifically includes: S51: According to the classification and priority sorting results in S4, different categories of events and information are mapped to the corresponding three-dimensional coordinate space, and the event data is converted into three-dimensional objects through the WebGL rendering engine. Each object is given a different color, shape and size according to its classification. Events with higher priority are displayed in a more eye-catching way in the visualization interface; S52: Generate a 3D visualization interface using WebGL technology. The layout of the 3D space is designed based on the classification and priority of events. High-priority events are placed at the core of the interface, allowing users to rotate, scale, and move 3D objects through mouse or touch operations to obtain different perspectives. S53: monitors data changes from the S3 database, and dynamically updates the display status of the three-dimensional object according to the new priority sorting results. Specifically, when a high-priority event is detected, the three-dimensional interface will automatically refresh the display and insert the new high-priority event into the visualization interface; S54: The visualization interface also supports users to manually filter events and data, allowing users to filter the displayed content by category, time range or priority through the filtering tools on the interface.

9. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 1, characterized in that: The S6 specifically includes: S61: When the user interacts with the 3D visualization interface in S5, the user's operation behavior is recorded in real time, including clicks, filtering, zooming, rotation, and data filtering conditions; S62: Analyze the user preference using the collected user operation behavior data using a behavior analysis algorithm, wherein the behavior analysis algorithm calculates the user's preference weight according to the user's operation frequency, operation duration, event category of interest, and screening conditions; S63: Based on the user preference analysis result, analyzing the user preference weight, determining the category of data or events that need to be displayed first; S64: Dynamically adjust the data display content based on the preferences analyzed from the user's operation behavior, and prioritize loading data of related categories based on the user's filtering conditions or focus, thereby reducing unnecessary data loading and display.

10. The method for realizing comprehensive display of enterprise management information using Web-based technology according to claim 1, characterized in that: The S7 specifically includes: S71: Set a unique identity for each user, and verify the user's identity through the authentication mechanism when the user logs in. When registering or allocating an account, each user will be assigned different roles, including administrators, financial personnel, and ordinary users; S72: defining permission sets for different roles according to the management requirements of the enterprise, with each role being associated with a predetermined set of data access permissions, including permissions to read, write, modify or delete predetermined data; S73: Classify data in enterprise management information and mark sensitive data, including financial statements, customer information and contracts; each piece of data is graded according to its sensitivity level and marked as public, restricted or confidential; S74: Based on the user's role and permission set, the role-based access control rules are applied. When a user requests to access a certain data, it is first checked whether the user's role has the corresponding permission; if the user's permission level is not higher than the sensitivity level of the data, the access request is denied; S75: Dynamically adjust roles and permissions based on changes in user responsibilities. When a user's position changes or job responsibilities are adjusted, the system administrator can modify their role assignment to ensure that they have data access permissions consistent with their new responsibilities.

Citation Information

Patent Citations

  • Enterprise internal risk management early warning device system

    CN117132114A

  • Hot-pluggable distributed heterogeneous data source data scheduling processing system

    CN117312103A

  • Data large screen generation method and system based on AI large language model

    CN117493427A

  • WebGL-based three-dimensional graph visualization system

    CN117523079A

  • Smart terminal display system based on data resources

    CN117829096A

Cited By

  • Cloud computing platform data security access method and system

    CN119316228A

  • Data right confirmation method based on subject and object binding

    CN119337407A

  • User data processing optimization system oriented to cloud computing environment

    CN119668513A

  • A user data processing optimization system for cloud computing environment

    CN119668513B

  • Multidimensional data analysis method and device based on holography

    CN119719657A