Intelligent enterprise comprehensive management platform based on AI knowledge base

Abstract

The application discloses an intelligent enterprise comprehensive management platform based on an AI knowledge base, and relates to the technical field of enterprise comprehensive management.The application comprises three modules, namely, a knowledge division module, an employee division module and a knowledge pushing module.The knowledge division module divides knowledge priorities according to business influences, and marks knowledge effective time periods and adaptive posts.The employee division module screens daily idle time periods of employees, and divides the idle time periods into process connection types and independent control types according to business characteristics.The knowledge pushing module matches the effective time periods of knowledge and the idle time periods of employees, dynamically adjusts the pushing of knowledge in the form of core points or complete content, simultaneously carries out real-time state secondary verification before pushing, and sets time limit and effect early warning rules according to priorities.The application realizes accurate and time-effective adaptive directional pushing of enterprise knowledge, and improves the utilization efficiency of enterprise knowledge.

Description

Technical Field

[0001] This invention relates to the field of enterprise integrated management technology, specifically to an intelligent enterprise integrated management platform based on an AI knowledge base. Background Technology

[0002] In existing enterprise integrated management scenarios, the management and dissemination of enterprise knowledge have the following shortcomings:

[0003] First, the priority of enterprise knowledge was not divided and corresponding effective time periods were not bound, which easily leads to the continuous push of outdated knowledge and the failure to deliver core knowledge in a timely manner, affecting business compliance and efficiency.

[0004] Secondly, the system fails to effectively utilize employees' free time periods, does not differentiate between different types of free time based on the characteristics of business continuity, and simply uses a uniform approach to push knowledge. This results in pushing long articles during task breaks or fragmented information during periods when in-depth reading is possible, leading to poor adaptability.

[0005] Third, the length of enterprise knowledge push is fixed and does not dynamically adjust according to free time and knowledge priority, making it difficult to balance the completeness of knowledge delivery with the need for uninterrupted work.

[0006] Fourth, the lack of a targeted and timely early warning mechanism ultimately resulted in employees not being reminded to update their learning before core knowledge became obsolete, while excessive early warnings for non-core knowledge caused information overload.

[0007] Therefore, there is an urgent need for an intelligent enterprise integrated management platform based on AI knowledge base. Summary of the Invention

[0008] To address the shortcomings of existing technologies, this invention provides an intelligent enterprise integrated management platform based on an AI knowledge base, which solves the problems of inaccurate enterprise knowledge delivery, insufficient timeliness and adaptability to different scenarios.

[0009] To achieve the above objectives, the present invention provides the following technical solution: an intelligent enterprise integrated management platform based on an AI knowledge base, comprising:

[0010] The knowledge segmentation module divides enterprise knowledge into three priorities based on the degree of business impact, marks the effective working period and corresponding start and end dates for each piece of enterprise knowledge, and sets a job list that matches enterprise knowledge. The job list corresponds one-to-one with enterprise positions, and the enterprise knowledge is only pushed to employees in the positions on the list. The start and end dates include the official effective date and the expiration date of the enterprise knowledge.

[0011] The employee segmentation module allows the enterprise business system to obtain the task list of employees in each position in real time, filter out the daily free time periods of employees, and classify them into process-connecting free time and autonomous free time according to business characteristics. The process-connecting free time refers to the free time period between two consecutive business tasks, which is used to connect the processes before and after. The autonomous free time refers to the free time period after all tasks are completed or there is no clear task arrangement for the day.

[0012] The knowledge push module matches the effective working time period of each piece of enterprise knowledge with the daily free time period of the corresponding employees, determines the push duration based on the matching results, dynamically adjusts the length of the enterprise knowledge push based on the push duration, and performs a real-time secondary status verification before pushing enterprise knowledge.

[0013] As a further aspect of the present invention, enterprise knowledge is divided into three priorities based on its degree of business impact. The specific operation is as follows:

[0014] Analyze all standardized business processes of the enterprise, break them down into specific steps that cannot be omitted, assign a unique process code to each step, and bind each piece of enterprise knowledge to the corresponding step.

[0015] Based on the impact of process interruption, enterprise knowledge is divided into three priorities: if there is no temporary alternative after the interruption of the linked process, it is classified as a first-level priority; if there is a temporary alternative after the interruption of the linked process, it is classified as a second-level priority; if the interruption of the linked process does not affect the operation of the process, it is classified as a third-level priority.

[0016] As a further aspect of the present invention, the specific steps for defining the effective time period for each piece of enterprise knowledge annotation are as follows:

[0017] For first-priority knowledge, bind it to be valid at all times, that is, it is valid at any time of day without time restrictions;

[0018] For secondary priority knowledge, it is bound to be valid only on working days as specified by the company.

[0019] For level 3 priority knowledge, it is bound to be valid only during the specific business scenario and is only valid during the time period when the corresponding business scenario occurs.

[0020] As a further aspect of the present invention, categorizing idle time into process connection type and autonomous control type based on business characteristics specifically includes:

[0021] If the idle time period is connected to a process that is marked as a first- or second-level priority knowledge binding process, then it is classified as an idle process connection.

[0022] If there are no preceding or following tasks during an idle period, or if the preceding and following tasks are all third-priority knowledge-bound processes, then it is classified as an autonomously controlled idle period.

[0023] As a further aspect of the present invention, the specific operation for obtaining the push duration based on the matching result is as follows:

[0024] Retrieve the start and end dates of each piece of enterprise knowledge, retaining only enterprise knowledge that is currently in effect;

[0025] The system analyzes the time periods corresponding to two categories of idle time: idle time related to the connection between enterprise knowledge and the corresponding employee's workflow, and idle time related to self-management. It then matches these idle time periods with the enterprise knowledge currently in effect.

[0026] If there is an overlap, the overlapping time period is marked as a candidate push time period, and the push duration is recorded as the continuous length of the overlapping time period. At the same time, if the candidate push time period is obtained from the idle time of the process connection type, it is also necessary to mark the task process link attribute and the connection cannot be interrupted. If the candidate push time period is obtained from the idle time of the autonomous control type, it is also necessary to mark the autonomous controllable mark.

[0027] As a further aspect of the present invention, dynamically adjusting the length of enterprise knowledge push notifications based on push duration specifically includes:

[0028] For each piece of enterprise knowledge, core key point form knowledge and complete content form knowledge are generated synchronously. The preset base time for transmitting core key point form knowledge is T1, and the base time for transmitting complete content form knowledge is T2, where T2 > T1. The core key point form knowledge refers to the set of essential key information extracted from enterprise knowledge, and the complete content form knowledge refers to the complete information set that includes core key point form knowledge and all supporting information.

[0029] Inferring the completeness of enterprise knowledge transmission during idle periods based on the type of employee idle time;

[0030] Based on the integrity inference results, a second calibration is performed to obtain the final push length.

[0031] As a further aspect of the present invention, the specific steps for inferring the integrity of enterprise knowledge transmission based on the type of employee idle time periods are as follows:

[0032] For idle periods related to process connections, extract the continuous duration T marked in the candidate push period and determine whether core key morphological knowledge can be transmitted. If T≥T1, it indicates that core key morphological knowledge can be transmitted. If T<T1, it needs to be marked as a period to be postponed.

[0033] For idle time slots with autonomous control, if T≥T2, it indicates that complete content morphology knowledge can be transmitted; if T1≤T<T2, it indicates that only core morphology knowledge can be transmitted; if T<T1, it needs to be marked as a time slot to be postponed.

[0034] As a further aspect of the present invention, the secondary calibration to obtain the final push length specifically includes:

[0035] For idle processes related to workflow connection: If the enterprise knowledge is of first-priority level, it will be calibrated as core point knowledge regardless of whether T ≥ T1; if the enterprise knowledge is of second-priority level, it will be calibrated as core point knowledge only when T ≥ T1; if T < T1, it will be temporarily stored and not pushed, and will be carried over to the next idle process of autonomous control; if the enterprise knowledge is of third-priority level, it will only retain the qualification to adapt to idle processes of autonomous control.

[0036] For self-managed idle time: If the enterprise knowledge is of first-priority level, when T≥T2, it is calibrated to core key knowledge and full content entry, which employees can click to view independently; when T1≤T<T2, it is calibrated to core key knowledge. If the enterprise knowledge is of second-priority level, when T≥T2, it is calibrated to full content; when T1≤T<T2, it is calibrated to core key knowledge; if T<T1, it needs to be marked as pending extension. If the enterprise knowledge is of third-priority level, when T≥T2, it is calibrated to full content; otherwise, it is temporarily stored and not pushed to avoid occupying fragmented idle time.

[0037] As a further aspect of the present invention, the knowledge push module also includes a timeliness warning rule for binding each piece of enterprise knowledge based on priority differences, specifically as follows:

[0038] If the knowledge is of first or second priority, then an automatic warning needs to be issued before the expiration date when the final warning time is set.

[0039] If it is a level 3 priority knowledge, no automatic warning is required. It should only be automatically unbound from the corresponding position and removed from the push queue after it becomes invalid, but the archive query permission should be retained.

[0040] As a further aspect of the present invention, the step of constructing a final early warning time before the expiration date specifically includes:

[0041] The warning interval is defined as TG. The base date is calculated by working backward from the expiration date of the enterprise knowledge, i.e., base date = expiration date of enterprise knowledge - TG, where TG > T2.

[0042] Retrieve all candidate push time slots for employees in the first and second priority knowledge adaptation positions on the expiration date, retain only the candidate push time slots with a duration of ≥T1, remove the candidate push time slots for which employees have declared temporary busyness, and include the remaining time slots in the candidate idle time slot list for the expiration date;

[0043] From the list of candidate idle time slots for the expiration date, select candidate push time slots whose end time is ≤ the base date;

[0044] Using the end time of each candidate push period as the calculation node, the time difference between the end time and the base date is calculated. The time differences are sorted from smallest to largest, and the two candidate push periods with the smallest and second smallest time differences are selected. Any time between the end times of these two candidate push periods is taken as the final warning time.

[0045] This invention provides an intelligent enterprise integrated management platform based on an AI knowledge base, which has the following advantages compared with existing technologies:

[0046] (1) This invention prioritizes knowledge according to its impact on business and binds it to corresponding effective time periods and dedicated job lists to achieve hierarchical management and targeted delivery of enterprise knowledge, avoid ineffective cross-job delivery, ensure timely delivery of core business knowledge, and improve the efficiency of enterprise knowledge utilization.

[0047] (2) This invention classifies employees’ free time according to business characteristics and dynamically matches core points or complete content knowledge with push duration. Among them, the free time for process connection type pushes lightweight core information, and the free time for autonomous control type pushes complete knowledge. This design realizes accurate adaptation of knowledge form and free time scenario, which does not affect core work and maximizes the transmission of enterprise knowledge.

[0048] (3) The present invention verifies the validity of employees’ free time before pushing, promptly postpones invalid pushes and archives them, avoids problems such as invalid knowledge misleading business and push time conflicts, and ensures the timeliness and reliability of knowledge push. Attached Figure Description

[0049] Figure 1 This is the system principle block diagram of the present invention;

[0050] Figure 2 A flowchart illustrating the steps involved in adjusting the length of enterprise knowledge push notifications in this invention. Detailed Implementation

[0051] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0052] like Figure 1 This invention provides an intelligent enterprise integrated management platform based on an AI knowledge base;

[0053] As an embodiment of this application, the specific steps include the following:

[0054] The knowledge segmentation module divides enterprise knowledge into three priorities based on the degree of business impact, marks the effective working period and corresponding start and end dates for each piece of enterprise knowledge, and sets a job list that matches enterprise knowledge. The job list corresponds one-to-one with enterprise positions, and the enterprise knowledge is only pushed to employees in the positions on the list. The start and end dates include the official effective date and the expiration date of the enterprise knowledge.

[0055] The employee segmentation module allows the enterprise business system to obtain the task list of employees in each position in real time, filter out the daily free time periods of employees, and classify them into process-connecting free time and autonomous free time according to business characteristics. The process-connecting free time refers to the free time period between two consecutive business tasks, which is used to connect the processes before and after. The autonomous free time refers to the free time period after all tasks are completed or there is no clear task arrangement for the day.

[0056] The knowledge push module matches the effective working time period of each piece of enterprise knowledge with the daily free time period of the corresponding employees, determines the push duration based on the matching results, dynamically adjusts the length of the enterprise knowledge push based on the push duration, and performs a real-time secondary status verification before pushing enterprise knowledge.

[0057] As a second embodiment of this application, it is implemented based on the first embodiment, except that this embodiment includes:

[0058] The knowledge segmentation module categorizes enterprise knowledge into three priorities based on its impact on business operations. The specific steps are as follows:

[0059] Analyze all standardized business processes of the enterprise, break them down into specific steps that cannot be omitted, assign a unique process code to each step, and bind each piece of enterprise knowledge to the corresponding step.

[0060] For example, the "Finished Goods Outbound Scanning Specification" is linked to the finished goods outbound process - scan confirmation stage, and the corresponding process code is recorded as CC-003; the "Employee Social Security Contribution Details" is linked to the personnel and salary process - social security declaration stage, and the corresponding process code is recorded as RS-005.

[0061] Based on the impact of process disruptions, enterprise knowledge is divided into three priorities, specifically including:

[0062] If the binding process is interrupted and there is no temporary alternative, directly causing the entire corresponding business process to stop, it indicates that the enterprise knowledge is essential and irreplaceable in the process, and it is classified as a first-level priority.

[0063] If a binding process is interrupted, there is a temporary alternative solution, and it only leads to a decrease in efficiency and an increase in operating costs for the corresponding process, but does not affect the operation of the entire process, then it indicates that the enterprise's knowledge is the optimal but not the only basis for the execution of the process, and it is classified as a secondary priority.

[0064] If the interruption of the binding link does not affect the operation of the process, and the enterprise knowledge is only used to optimize the efficiency of the link operation or improve the job skills, it indicates that there is no need for a replacement and the link can be omitted, and it is classified as a level three priority.

[0065] Each piece of enterprise knowledge is labeled with a valid time period, which is strongly correlated with priority and includes:

[0066] For first-priority knowledge, bind it to be valid at all times, that is, it is valid at any time of day without time restrictions;

[0067] For secondary priority knowledge, it is bound to be valid only on working days as stipulated by the company, and it will be suspended from being pushed on non-working days, such as weekends and holidays;

[0068] For Level 3 priority knowledge, it is bound to be valid only during the time period when the corresponding business scenario occurs.

[0069] For each piece of enterprise knowledge, the start and end dates of its effective period are additionally marked. The start and end dates include the official effective date and the expiration date of the knowledge, thus clarifying the overall effective scope of the knowledge.

[0070] For example, the secondary priority knowledge "Monthly Report Preparation Specification" specifies the start and end dates as: the effective date to the last working day of December of the current year, and the effective working period as: the working period of the working days stipulated by the company;

[0071] After marking the effective working period and start and end dates for each piece of enterprise knowledge, it is also necessary to set up a job list that matches the enterprise knowledge. The job list corresponds one-to-one with the enterprise positions, and the knowledge is only pushed to the positions in the list.

[0072] Different levels of corporate knowledge correspond to the core work or skill requirements of specific positions. If an unsuitable position receives this knowledge, it will not only be useless, but it will also distract attention.

[0073] The employee segmentation module allows the enterprise business system to obtain the task lists of employees in each position in real time and filter out the employees' daily free time slots. The specific operation is as follows:

[0074] Before starting work each day, the enterprise business system automatically synchronizes all task lists for all employees in all positions, clearly specifying the start and end times of each task and the tasks that follow.

[0075] The system automatically removes the execution times of all tasks in the task list, and treats the remaining continuous time segments without task coverage as idle time segments, while marking the task process links before and after each idle time segment.

[0076] If an employee adds, cancels, or adjusts the duration of their tasks for the day, the business system will synchronize the changes in real time and automatically adjust the available time slots, pushing the updated available list to the employee's terminal for verification.

[0077] After obtaining the idle time slots, they are categorized according to business characteristics. The specific steps are as follows:

[0078] Based on the business connection attributes of idle time periods, define idle time periods as either process connection type or autonomous control type;

[0079] The availability of idle time slots alone is insufficient to support push decisions. For the same amount of idle time, in addition to differences in business scenarios, employees' ability to absorb knowledge also varies greatly. If the knowledge is not categorized according to business characteristics, it will lead to the inability to accurately push knowledge to employees in the future.

[0080] The aforementioned idle time in process connection refers to the idle time period between two consecutive business tasks, used to connect the processes before and after. Employees need to be ready to enter the next task at any time and have no room for independent control.

[0081] The aforementioned free time refers to the free time period when all tasks for the day have been completed or there are no specific tasks assigned, during which employees can manage their time independently without having to respond to tasks at any time.

[0082] The system automatically categorizes tasks based on the attributes of the sequential steps within the idle time slots. These task step attributes are steps with pre-defined priority information.

[0083] If the idle time period is connected to a process that is marked as a first- or second-level priority knowledge binding process, then it is classified as an idle process connection.

[0084] First- or second-level priority knowledge is tied to the core and daily business processes of an enterprise. During the idle time between these processes, employees need to prioritize ensuring the smooth transition of tasks to avoid interruption of core business. This is consistent with the characteristics of process connection type that requires employees to be on standby at all times and has no room for autonomy.

[0085] If there are no preceding or following tasks during an idle time period, or if the preceding and following tasks are all third-priority knowledge-bound processes, then it is classified as an autonomously controlled idle time period.

[0086] The absence of preceding or following tasks corresponds to scenarios without task constraints, which aligns with the attribute of autonomous control. Meanwhile, the third-level priority knowledge is bound to non-core business processes. During the idle time between these processes, employees do not need to respond to core tasks at any time, and there is no business constraint pressure.

[0087] When checking the idle list, each employee needs to manually correct the system's classification results. For example, if an idle item in the process connection category is mistakenly identified as an idle item in the autonomous control category, the specific reason needs to be noted after correction, and the correction results should be updated in real time and automatically archived to the business system.

[0088] The knowledge push module matches the effective working time slots of each piece of enterprise knowledge with the corresponding time slots of employees in the relevant positions, specifically those for workflow-related and autonomous-management-related free time. The push duration is determined based on the matching results. The specific operation is as follows:

[0089] Retrieve the start and end dates of each piece of enterprise knowledge, retaining only enterprise knowledge that is currently in effect;

[0090] Enterprise knowledge has a clear time limit. For example, operating procedures are revised with the iteration of equipment. If outdated enterprise knowledge is pushed, it will cause employees to carry out their work according to the old standards, which will cause compliance and security risks. On the other hand, the push of outdated enterprise knowledge has no actual business value and is invalid information. If knowledge within the effective period is not screened first, the system will need to perform matching and calculation on all knowledge, which will greatly increase the computing burden.

[0091] The system analyzes the time periods corresponding to two categories of idle time: idle time related to the connection between enterprise knowledge and the corresponding employee's workflow, and idle time related to self-management. It then matches these idle time periods with the enterprise knowledge currently in effect.

[0092] The core characteristics of idle time in process connection type are that it is always ready and easy to be interrupted, and it is only suitable for core key knowledge. In contrast, the core characteristics of idle time in autonomous control type are that it is unrestrained, can be read in depth, and is suitable for complete content knowledge. If the type is not distinguished and the effective time period of knowledge is arbitrarily matched with all idle time periods, there will be inappropriate scenarios where idle time in process connection type is matched with complete content knowledge.

[0093] The core essential knowledge refers to the set of essential information extracted from enterprise knowledge that cannot be omitted. Only the core content that supports the bottom line of business operations is retained, and all redundant information such as background explanations, supplementary interpretations, and case extensions are removed. It is suitable for idle time periods of process connection that are always on standby and easily interrupted.

[0094] The complete content form knowledge refers to a complete set of information that includes core key form knowledge and all supporting information. It retains the bottom line of business operations while supplementing it with detailed interpretations, supporting materials, and in-depth explanations, making it suitable for unconstrained and deeply readable free time periods.

[0095] If there is an overlap, the overlapping time period is marked as a candidate push time period, and the push duration is recorded as the continuous length of the overlapping time period. At the same time, if the candidate push time period is obtained from the idle time of the process connection type, it is also necessary to mark the task process link attribute and the connection cannot be interrupted. If the candidate push time period is obtained from the idle time of the autonomous control type, it is also necessary to mark the autonomous controllable mark.

[0096] Before pushing enterprise knowledge, a real-time secondary status verification is required. The specific steps are as follows:

[0097] Within a fixed time period before the enterprise knowledge is pushed out (this fixed time period needs to be set in advance according to the actual situation), the system automatically verifies the validity of the candidate push time period: if the time period is occupied due to the addition or adjustment of employee tasks, or the effective time period of the knowledge has entered the near-expiration / expiration period, the time period is immediately marked as invalid and the push is suspended.

[0098] The system synchronously verifies the current work status of employees, including the status automatically determined by the system and the temporary status declared by the employees themselves: if an employee is performing a task or has declared that they are temporarily busy, the push will be immediately paused and the system will automatically postpone the enterprise knowledge to the next candidate push time period that coincides with the effective time period of the enterprise knowledge (prioritizing idle time periods of the same type). The postponement record needs to be archived synchronously and the reason for postponement should be marked, such as the time period being occupied or the employee being temporarily busy.

[0099] When enterprise knowledge is nearing its expiration date, it is necessary to assign corresponding time-sensitive warning rules to each piece of enterprise knowledge based on its priority. These rules include:

[0100] If the knowledge is of priority level one or two, then an automatic warning needs to be issued at the final warning time before the expiration date. The specific operation is as follows:

[0101] The warning interval is defined as TG. The base date is calculated by working backward from the expiration date of the enterprise knowledge, i.e., base date = expiration date of enterprise knowledge - TG, where TG > T2.

[0102] TG's buffer design ensures that the time from the base date to the expiration date is sufficient to cover the transmission needs of both forms of knowledge, avoiding the situation where employees cannot receive complete information due to insufficient time.

[0103] Retrieve all candidate push time slots (including idle slots for process connection and idle slots for autonomous disposal) of employees in the first and second priority knowledge adaptation positions on the expiration date, retain only the candidate push time slots with a duration of ≥T1, and remove the candidate push time slots for which employees have declared temporary busyness. The remaining time slots are included in the candidate idle time slot list for the expiration date.

[0104] From the list of candidate idle time slots for the expiration date, select candidate push time slots whose end time is ≤ base date to ensure that the warning time falls within the buffer between the base date and the expiration date, allowing sufficient time for employees to digest the knowledge;

[0105] Using the end time of each candidate push period as the calculation node, calculate the time difference between the end time and the base date, sort the time differences from smallest to largest, filter out the two candidate push periods with the smallest and second smallest time differences, and randomly select one time between the end times of these two candidate push periods as the final warning time.

[0106] If it is a level 3 priority knowledge, no automatic warning is required. It should only be automatically unbound from the corresponding position and removed from the push queue after it becomes invalid, but the archive query permission should be retained.

[0107] As a third embodiment of this application, this embodiment further discloses a method for dynamically adjusting the length of enterprise knowledge push notifications based on push duration, building upon embodiments one and two. Figure 2 As shown, the specific content includes:

[0108] For each piece of enterprise knowledge, core key point form knowledge and complete content form knowledge are generated synchronously. The basic time for transmitting core key point form knowledge is preset to T1 (adapting to fast reception, without redundant information), and the basic time for transmitting complete content form knowledge is T2 (including full text, illustrations and interpretation, requiring in-depth reading). Among them, T2 > T1. Both are set by the business department in combination with the complexity of enterprise knowledge and are bound to the knowledge priority.

[0109] Inferring the completeness of enterprise knowledge transmission during idle periods based on the type of employee idle time:

[0110] For idle periods in the process connection category, extract the continuous duration T marked in the candidate push period. Since this type of period may be interrupted by the next task at any time, only determine whether the core key morphological knowledge can be transmitted (no need to determine T2). If T≥T1, it means that the core key morphological knowledge can be transmitted. If T<T1, it needs to be marked as a period to be postponed.

[0111] For idle time slots with autonomous control, if T≥T2, it indicates that complete content morphology knowledge can be transmitted; if T1≤T<T2, it indicates that only core morphology knowledge can be transmitted; if T<T1, it indicates that effective transmission conditions are not available at the moment and it needs to be marked as a time slot to be postponed.

[0112] Based on the completeness inference results, and by overlaying the business characteristics of idle types and the mandatory reachability of knowledge levels, a second calibration is performed to determine the final push length:

[0113] For idle processes related to workflow transitions (adapting to easily interrupted scenarios, prioritizing the protection of core information):

[0114] If the enterprise knowledge is a first-priority knowledge, then regardless of whether T is greater than or equal to T1, it will be calibrated as core knowledge to ensure that key knowledge is delivered without being limited by time.

[0115] If the enterprise knowledge is secondary priority knowledge, it will be calibrated as core key form knowledge only if T≥T1. If T<T1, it will be temporarily stored and not pushed, and will be postponed to the next autonomously controllable idle time.

[0116] If the enterprise knowledge is a level 3 priority knowledge, the idle push for process connection will be directly excluded, and only the idle adaptation qualification for autonomous control will be retained to avoid non-core knowledge from interfering with the connection of core tasks.

[0117] For autonomously manageable idle time (adapted to in-depth reading scenarios, balancing integrity and priority):

[0118] If the enterprise knowledge is of first-level priority, when T≥T2, it is calibrated as core key point form knowledge and complete content entry. The complete content entry is available for employees to click and view independently, ensuring priority access to core information; when T1≤T<T2, it is calibrated as core key point form knowledge.

[0119] If the enterprise knowledge is of secondary priority, when T≥T2, it is calibrated to complete content form knowledge; when T1≤T<T2, it is calibrated to core point form knowledge; if T<T1, it needs to be marked as a period to be postponed.

[0120] If the enterprise knowledge is a level 3 priority knowledge, when T≥T2, it will be calibrated to a complete content form knowledge; otherwise, it will be temporarily stored and not pushed to avoid occupying fragmented free time.

[0121] Based on the calibration results, a personalized push content package for each employee is generated for each piece of enterprise knowledge, including push length, candidate push time period, available time type, and push duration. The push length is either core key knowledge or complete content knowledge.

[0122] Some of the data in the above formulas are numerical calculations with dimensions removed, and the contents not described in detail in this specification are all prior art known to those skilled in the art.

[0123] The above embodiments are only used to illustrate the technical methods of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical methods of the present invention without departing from the spirit and scope of the technical methods of the present invention.

Claims

1. An intelligent enterprise integrated management platform based on an AI knowledge base, characterized in that: include: The knowledge segmentation module divides enterprise knowledge into three priorities based on the degree of business impact, marks the effective working period and corresponding start and end dates for each piece of enterprise knowledge, and sets a job list that matches enterprise knowledge. The job list corresponds one-to-one with enterprise positions, and the enterprise knowledge is only pushed to employees in the positions on the list. The start and end dates include the official effective date and the expiration date of the enterprise knowledge. The employee segmentation module allows the enterprise business system to obtain the task list of employees in each position in real time, filter out the daily free time periods of employees, and classify them into process-connecting free time and autonomous free time according to business characteristics. The process-connecting free time refers to the free time period between two consecutive business tasks, which is used to connect the processes before and after. The autonomous free time refers to the free time period after all tasks are completed or there is no clear task arrangement for the day. The knowledge push module matches the effective working time period of each piece of enterprise knowledge with the daily free time period of the corresponding employees, determines the push duration based on the matching results, dynamically adjusts the length of the enterprise knowledge push based on the push duration, and performs a real-time secondary status verification before pushing enterprise knowledge.

2. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 1, characterized in that, Enterprise knowledge is divided into three priorities based on its business impact. The specific steps are as follows: Analyze all standardized business processes of the enterprise, break them down into specific steps that cannot be omitted, assign a unique process code to each step, and bind each piece of enterprise knowledge to the corresponding step. Based on the impact of process interruption, enterprise knowledge is divided into three priorities: if there is no temporary alternative after the interruption of the linked process, it is classified as a first-level priority; if there is a temporary alternative after the interruption of the linked process, it is classified as a second-level priority; if the interruption of the linked process does not affect the operation of the process, it is classified as a third-level priority.

3. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 1, characterized in that, The specific steps for labeling the effective period of each enterprise knowledge entry are as follows: For first-priority knowledge, bind it to be valid at all times, that is, it is valid at any time of day without time restrictions; For secondary priority knowledge, it is bound to be valid only on working days as specified by the company. For level 3 priority knowledge, it is bound to be valid only during the specific business scenario and is only valid during the time period when the corresponding business scenario occurs.

4. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 1, characterized in that, Based on business characteristics, idle time can be categorized into process connection type and autonomous control type, specifically including: If the idle time period is connected to a process that is marked as a first- or second-level priority knowledge binding process, then it is classified as an idle process connection. If there are no preceding or following tasks during an idle period, or if the preceding and following tasks are all third-priority knowledge-bound processes, then it is classified as an autonomously controlled idle period.

5. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 1, characterized in that, The specific steps to obtain the push duration based on the matching results are as follows: Retrieve the start and end dates of each piece of enterprise knowledge, retaining only enterprise knowledge that is currently in effect; The system analyzes the time periods corresponding to two categories of idle time: idle time related to the connection between enterprise knowledge and the corresponding employee's workflow, and idle time related to self-management. It then matches these idle time periods with the enterprise knowledge currently in effect. If there is an overlap, the overlapping time period is marked as a candidate push time period, and the push duration is recorded as the continuous length of the overlapping time period. At the same time, if the candidate push time period is obtained from the idle time of the process connection type, it is also necessary to mark the task process link attribute and the connection cannot be interrupted. If the candidate push time period is obtained from the idle time of the autonomous control type, it is also necessary to mark the autonomous controllable mark.

6. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 1, characterized in that, The specific adjustments to the length of enterprise knowledge push notifications based on push duration include: For each piece of enterprise knowledge, core key point form knowledge and complete content form knowledge are generated synchronously. The preset base time for transmitting core key point form knowledge is T1, and the base time for transmitting complete content form knowledge is T2, where T2 > T1. The core key point form knowledge refers to the set of essential key information extracted from enterprise knowledge, and the complete content form knowledge refers to the complete information set that includes core key point form knowledge and all supporting information. Inferring the completeness of enterprise knowledge transmission during idle periods based on the type of employee idle time; Based on the integrity inference results, a second calibration is performed to obtain the final push length.

7. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 6, characterized in that, The specific steps for inferring the integrity of enterprise knowledge transfer based on the type of employee idle time are as follows: For idle periods related to process connections, extract the continuous duration T marked in the candidate push period and determine whether core key morphological knowledge can be transmitted. If T≥T1, it indicates that core key morphological knowledge can be transmitted. If T<T1, it needs to be marked as a period to be postponed. For idle time slots with autonomous control, if T≥T2, it indicates that complete content morphology knowledge can be transmitted; if T1≤T<T2, it indicates that only core morphology knowledge can be transmitted; if T<T1, it needs to be marked as a time slot to be postponed.

8. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 6, characterized in that, The final push notification length, obtained through secondary calibration, specifically includes: For idle processes related to workflow connection: If the enterprise knowledge is of first-priority level, it will be calibrated as core point knowledge regardless of whether T ≥ T1; if the enterprise knowledge is of second-priority level, it will be calibrated as core point knowledge only when T ≥ T1; if T < T1, it will be temporarily stored and not pushed, and will be carried over to the next idle process of autonomous control; if the enterprise knowledge is of third-priority level, it will only retain the qualification to adapt to idle processes of autonomous control. For self-managed idle time: If the enterprise knowledge is of first-priority level, when T≥T2, it is calibrated to core key knowledge and full content entry, which employees can click to view independently; when T1≤T<T2, it is calibrated to core key knowledge. If the enterprise knowledge is of second-priority level, when T≥T2, it is calibrated to full content; when T1≤T<T2, it is calibrated to core key knowledge; if T<T1, it needs to be marked as pending extension. If the enterprise knowledge is of third-priority level, when T≥T2, it is calibrated to full content; otherwise, it is temporarily stored and not pushed to avoid occupying fragmented idle time.

9. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 1, characterized in that, The knowledge push module also includes binding corresponding time-sensitive warning rules to each piece of enterprise knowledge based on priority differences. The specific operation is as follows: If the knowledge is of first or second priority, then an automatic warning needs to be issued before the expiration date when the final warning time is set. If it is a level 3 priority knowledge, no automatic warning is required. It should only be automatically unbound from the corresponding position and removed from the push queue after it becomes invalid, but the archive query permission should be retained.

10. The intelligent enterprise integrated management platform based on AI knowledge base according to claim 9, characterized in that, The specific steps for establishing the final early warning time before the expiration date include: The warning interval is determined as TG. The base date is calculated by working backward from the time point of the enterprise knowledge expiration date, that is, the base date = the time point of the enterprise knowledge expiration date - TG, where TG > T2; Retrieve all candidate push time slots for employees in the first and second priority knowledge adaptation positions on the expiration date, retain only the candidate push time slots with a duration of ≥T1, remove the candidate push time slots for which employees have declared temporary busyness, and include the remaining time slots in the candidate idle time slot list for the expiration date; From the list of candidate idle time slots for the expiration date, select candidate push time slots whose end time is ≤ the base date; Using the end time of each candidate push period as the calculation node, the time difference between the end time and the base date is calculated. The time differences are sorted from smallest to largest, and the two candidate push periods with the smallest and second smallest time differences are selected. Any time between the end times of these two candidate push periods is taken as the final warning time.

Images