Multi-team and multi-application-based on-duty system calculation method

Abstract

The invention provides an on-duty system calculation method based on multiple teams and multiple applications, and the method comprises the following steps: S1, team configuration: firstly, each on-duty team needs to be defined, and each team may have different professional fields and on-duty requirements; s2, application classification: classifying applications needing on-duty support, and determining different support levels and response time requirements according to factors of importance degrees, complexity and fault frequencies of the applications; according to the method, different template strategies can be configured for application dimensions of a team respectively, the diversity of duty is increased, a set of complete calculation index updating system and historical record insertion system is designed when the operator on duty is calculated, so that both preview adjustment and duty calculation are very accurate, and the working efficiency is improved. When an operator on duty and an on-duty date need to be adjusted, a large on-duty template does not need to be changed, and flexible adjustment of local operators on duty is naturally supported.

Description

Technical Field

[0001] The present invention relates to the technical field of duty systems, and in particular to a duty system calculation method based on multiple teams and multiple applications. Background Art

[0002] With the development of online car-hailing business, the company's business volume and staff size are also increasing. The business teams and business applications within the company need to arrange on-duty personnel every day to handle and troubleshoot the problem feedback of the day, and provide technical and business support to other teams of the company. The current on-duty system has problems such as poor visual page effects, difficulty in configuring templates, and disordered on-duty calculations, resulting in incorrect display of on-duty personnel for teams and applications, and no one knows how to adjust to display the correct calculation results;

[0003] The existing duty system has the following problems: poor visualization page effect, difficult configuration template, disordered duty calculation, high cost of correcting data, no support for customized duty and shift change, no support for team-dimensional duty dashboard and preview, etc. Therefore, a duty system calculation method based on multi-team and multi-application is proposed. Summary of the invention

[0004] In view of this, an embodiment of the present invention hopes to provide a duty system calculation method based on multiple teams and multiple applications to solve or alleviate the technical problems existing in the prior art and at least provide a beneficial option.

[0005] The technical solution of the embodiment of the present invention is implemented as follows: a duty system calculation method based on multiple teams and multiple applications, comprising the following steps:

[0006] S1. Team configuration: First, it is necessary to define each duty team. Each team may have different professional fields and duty requirements;

[0007] S2. Application classification: Classify the applications that require on-call support and determine different support levels and response time requirements based on the importance, complexity, and failure frequency of the applications;

[0008] S3. Skill matching: Based on the skills and experience of team members, a skill library or matching algorithm is established to ensure that each duty task can be assigned to a team member with corresponding capabilities;

[0009] S4. Duty Scheduling: Develop a scheduling algorithm that takes into account team members’ availability, preferences, and statutory rest time to generate a fair duty schedule;

[0010] S5. Incident response process: Define a clear incident response process to ensure that on-duty personnel can quickly identify and classify incidents and take action according to established procedures.

[0011] In some embodiments, in S1, the duty team includes team members, duty hours and scope of responsibilities.

[0012] In some embodiments, in S3, the steps of establishing a skill library are as follows:

[0013] S3-10, Skill Record: Create a skills profile for each employee to record their skills and expertise;

[0014] S3-11. Search and filter: Provide search and filter functions to quickly find employees with specific skills;

[0015] S3-12, Skills Assessment: Regularly assess employees’ skills to ensure that the information in the skills database is up to date;

[0016] S3-13, Skill Development: Identify skill gaps and provide employees with training and development opportunities to enhance the overall capabilities of the organization;

[0017] S3-14. Reporting and analysis: Generate skills reports to help management analyze the skills status of the organization and provide a basis for strategic planning.

[0018] In some embodiments, in S3, the steps of the matching algorithm are as follows:

[0019] S3-20, Team and Skills Database: The system first needs to build a database containing all team members and their skills, qualifications, availability, and preferences;

[0020] S3-21, Task feature extraction: The system will extract relevant features from the duty tasks, which are used as input for the matching algorithm;

[0021] S3-22, Algorithm design: Design matching algorithms based on the characteristics of the team and the task;

[0022] S3-23, Matching process: The system matches the characteristics of the task with the skills and availability of team members. The algorithm will calculate according to the preset logic to find the best matching solution;

[0023] S3-24. Result output: The matching algorithm will output a result indicating that the team members are matched with the corresponding tasks.

[0024] In some embodiments, in S4, the scheduling algorithm is calculated when the person on duty is on duty. Since the duty configuration takes effect immediately on the same day, the initialized calculation index position is the first one. The calculation is based on the time range entered by the user. The data for today and later is calculated in real time, and the duty data before today depends on the historical record information.

[0025] In some embodiments, in S5, the incident response process includes incident reporting, assessment, allocation, processing and tracking.

[0026] The embodiment of the present invention has the following advantages due to the adoption of the above technical solution:

[0027] Through this method, the present invention can configure different template strategies for the application dimensions of the team, thereby increasing the diversity of duty. When calculating the person on duty, a complete calculation index update system and a historical record insertion system are designed, so that both the preview adjustment and the duty calculation are very accurate. When the person on duty and the duty date need to be adjusted, there is no need to change the large duty template, and flexible adjustment of local duty persons is naturally supported.

[0028] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present invention will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0030] Figure 1 is a flow chart of the present invention;

[0031] Figure 2 A flow chart for establishing a skills library for the present invention;

[0032] Figure 3 Flowchart of the matching algorithm of the present invention. DETAILED DESCRIPTION

[0033] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the present invention. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.

[0034] It should be noted that the terms "first", "second", "symmetrical", "array", etc. are only used to distinguish between description and position description purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the definition of "first", "symmetrical", etc. can explicitly or implicitly include one or more of these features; similarly, when the quantity of certain features is not limited in the form of words such as "two" or "three", it should be noted that this feature also explicitly or implicitly includes one or more feature quantities;

[0035] In the present invention, unless otherwise clearly specified and limited, the terms such as "installation", "connection", "fixation" and the like should be understood in a broad sense; for example, it can be a fixed connection, a detachable connection, or an integral molding; it can be a mechanical connection, a direct connection, welding, or an indirect connection through an intermediate medium, or it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood based on the description and drawings combined with specific circumstances.

[0036] The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0037] Embodiment 1

[0038] like Figure 1-Figure 2 As shown, an embodiment of the present invention provides a duty system calculation method based on multiple teams and multiple applications, including the following steps:

[0039] S1. Team configuration: First, it is necessary to define each duty team. Each team may have different professional fields and duty requirements;

[0040] S2. Application classification: Classify the applications that require on-call support and determine different support levels and response time requirements based on the importance, complexity, and failure frequency of the applications;

[0041] S3. Skill matching: Based on the skills and experience of team members, a skill library or matching algorithm is established to ensure that each duty task can be assigned to a team member with corresponding capabilities;

[0042] S4. Duty Scheduling: Develop a scheduling algorithm that takes into account team members’ availability, preferences, and statutory rest time to generate a fair duty schedule;

[0043] S5. Incident response process: Define a clear incident response process to ensure that on-duty personnel can quickly identify and classify incidents and take action according to established procedures.

[0044] In this embodiment, specifically, in S1, the duty team includes team members, duty hours and scope of responsibilities.

[0045] In this embodiment, specifically, in S3, the steps of establishing a skill library are as follows:

[0046] S3-10, Skill Record: Create a skills profile for each employee to record their skills and expertise;

[0047] S3-11. Search and filter: Provide search and filter functions to quickly find employees with specific skills;

[0048] S3-12, Skills Assessment: Regularly assess employees’ skills to ensure that the information in the skills database is up to date;

[0049] S3-13, Skill Development: Identify skill gaps and provide employees with training and development opportunities to enhance the overall capabilities of the organization;

[0050] S3-14. Reporting and analysis: Generate skills reports to help management analyze the skills status of the organization and provide a basis for strategic planning.

[0051] In this embodiment, specifically, in S3, the steps of the matching algorithm are as follows:

[0052] S3-20, Team and Skills Database: The system first needs to build a database containing all team members and their skills, qualifications, availability, and preferences;

[0053] S3-21, Task feature extraction: The system will extract relevant features from the on-duty tasks. These features are used as inputs for the matching algorithm. The features may include task type, required skills, urgency, estimated completion time, etc.

[0054] S3-22, Algorithm design: Design matching algorithms based on the characteristics of the team and the task. These algorithms may adopt strategies such as shortest job first, maximum idle time first, minimum cost first, or combine machine learning technology to optimize the matching process;

[0055] S3-23, Matching process: The system matches the characteristics of the task with the skills and availability of team members. The algorithm will calculate according to the preset logic to find the best matching solution;

[0056] S3-24. Result output: The matching algorithm will output a result indicating the matching of team members with corresponding tasks. This result will take into account whether the skills of team members are suitable for the task requirements and whether their workload is reasonable.

[0057] In this way, the matching algorithm helps the duty system to automatically and efficiently assign tasks, ensuring that each task is handled in a timely manner, while improving the team's job satisfaction and overall operational efficiency.

[0058] In this embodiment, specifically, in S4, the scheduling algorithm is calculated when the person on duty is on duty. Since the duty configuration takes effect immediately on the same day, the initialized calculation index position is the first position. The calculation is based on the time range passed in by the user. The data for today and later is calculated in real time, and the duty data before today depends on the historical record information.

[0059] In this embodiment, specifically, in S5, the event response process includes event reporting, evaluation, allocation, processing and tracking.

[0060] In this embodiment, specifically, business team: the company is divided into different teams according to business directions, such as order team, financial team, etc.

[0061] Business applications: Applications divided by the team based on modules and functions, such as the process of obtaining estimated prices for pricing and the process of placing orders, are all in different applications.

[0062] Duty strategy (type): Each business team arranges duty personnel according to their own team members and attributes, which includes the duty cycle (after a few days of rotation, the next round starts from the beginning), the number of duty days (how many days each person is on duty) and the corresponding duty personnel.

[0063] Strategy type: including weekday (general) duty, weekend duty and holiday duty, and the priority is holiday > weekend = weekday (general). For example, May 1, 2024 is both a holiday and a Wednesday. At this time, the holiday template will be used to calculate the duty person; which duty type is hit on a certain day is determined by the work and holiday calendar.

[0064] Scheduling status: If a team has configured a scheduling policy, it is scheduled; otherwise, it is not scheduled.

[0065] Customized duty and shift changes: After the duty template is configured, if the team wants to replace the person on duty on a certain day, the team leader can directly specify a custom person on duty on that day; or if person A in the team has something urgent to do on a certain day and wants to change shifts, the team leader can swap the duty dates of person A and person B to achieve the shift change effect. In both cases, there is no need to change the large duty template, only the data of a certain day and several days need to be adjusted.

[0066] Calculation index: It can be understood as the position of today's calculation; for example, if the duty cycle is 5 (rotating every 5 days), and the number of days on duty for each person is 2 (each person is on duty for 2 days), then the calculation index of the duty cycle is from 1 to 5. The calculation index of the number of days on duty is from 1 to 2. At 11:30 every night, there will be a scheduled task to update the calculation index. The update logic is: suppose today's duty cycle index is 3, that is, the third person is on duty, and the index of the number of days on duty is 1, that is, today has been on duty for one day, then after today's index is updated, the number of days on duty index +1 is 2, and the index of the duty cycle remains unchanged; tomorrow's index is updated, the index of the number of days on duty returns to 1, and the index of the duty cycle +1 is 4, and so on. That is, the index of the number of days on duty is updated first. After the index of the number of days on duty reaches the maximum value, the index of the number of days on duty is updated from the beginning, and the index of the duty cycle is +1. If the index of the duty cycle reaches the maximum value, the index of the duty cycle is updated from the beginning.

[0067] Duty history: At 11:30 every night, there will be a scheduled task to insert today's duty data into the duty history record. In this way, when viewing the team's duty calendar, you only need to calculate the data after today, and the data before today can be obtained from the history record.

[0068] Embodiment 2

[0069] like Figure 1 and Figure 3 As shown, an embodiment of the present invention provides a duty system calculation method based on multiple teams and multiple applications, including the following steps:

[0070] S1. Team configuration: First, it is necessary to define each duty team. Each team may have different professional fields and duty requirements;

[0071] S2. Application classification: Classify the applications that require on-call support and determine different support levels and response time requirements based on the importance, complexity, and failure frequency of the applications;

[0072] S3. Skill matching: Based on the skills and experience of team members, a skill library or matching algorithm is established to ensure that each duty task can be assigned to a team member with corresponding capabilities;

[0073] S4. Duty Scheduling: Develop a scheduling algorithm that takes into account team members’ availability, preferences, and statutory rest time to generate a fair duty schedule;

[0074] S5. Incident response process: Define a clear incident response process to ensure that on-duty personnel can quickly identify and classify incidents and take action according to established procedures.

[0075] In this embodiment, specifically, in S1, the duty team includes team members, duty hours and scope of responsibilities.

[0076] In this embodiment, specifically, in S3, the steps of establishing a skill library are as follows:

[0077] S3-10, Skill Record: Create a skills profile for each employee to record their skills and expertise;

[0078] S3-11. Search and filter: Provide search and filter functions to quickly find employees with specific skills;

[0079] S3-12, Skills Assessment: Regularly assess employees’ skills to ensure that the information in the skills database is up to date;

[0080] S3-13, Skill Development: Identify skill gaps and provide employees with training and development opportunities to enhance the overall capabilities of the organization;

[0081] S3-14. Reporting and analysis: Generate skills reports to help management analyze the skills status of the organization and provide a basis for strategic planning.

[0082] In this embodiment, specifically, in S3, the steps of the matching algorithm are as follows:

[0083] S3-20, Team and Skills Database: The system first needs to build a database containing all team members and their skills, qualifications, availability, and preferences;

[0084] S3-21, Task feature extraction: The system will extract relevant features from the on-duty tasks. These features are used as inputs for the matching algorithm. The features may include task type, required skills, urgency, estimated completion time, etc.

[0085] S3-22, Algorithm design: Design matching algorithms based on the characteristics of the team and the task. These algorithms may adopt strategies such as shortest job first, maximum idle time first, minimum cost first, or combine machine learning technology to optimize the matching process;

[0086] S3-23, Matching process: The system matches the characteristics of the task with the skills and availability of team members. The algorithm will calculate according to the preset logic to find the best matching solution;

[0087] S3-24. Result output: The matching algorithm will output a result indicating the matching of team members with corresponding tasks. This result will take into account whether the skills of team members are suitable for the task requirements and whether their workload is reasonable.

[0088] In this way, the matching algorithm helps the duty system to automatically and efficiently assign tasks, ensuring that each task is handled in a timely manner, while improving the team's job satisfaction and overall operational efficiency.

[0089] In this embodiment, specifically, in S4, the scheduling algorithm is calculated when the person on duty is on duty. Since the duty configuration takes effect immediately on the same day, the initialized calculation index position is the first position. The calculation is based on the time range passed in by the user. The data for today and later is calculated in real time, and the duty data before today depends on the historical record information.

[0090] In this embodiment, specifically, in S5, the event response process includes event reporting, evaluation, allocation, processing and tracking.

[0091] In this embodiment, specifically, business team: the company is divided into different teams according to business directions, such as order team, financial team, etc.

[0092] Business applications: Applications divided by the team based on modules and functions, such as the process of obtaining estimated prices for pricing and the process of placing orders, are all in different applications.

[0093] Duty strategy (type): Each business team arranges duty personnel according to their own team members and attributes, which includes the duty cycle (after a few days of rotation, the next round starts from the beginning), the number of duty days (how many days each person is on duty) and the corresponding duty personnel.

[0094] Strategy type: including weekday (general) duty, weekend duty and holiday duty, and the priority is holiday > weekend = weekday (general). For example, May 1, 2024 is both a holiday and a Wednesday. At this time, the holiday template will be used to calculate the duty person; which duty type is hit on a certain day is determined by the work and holiday calendar.

[0095] Scheduling status: If a team has configured a scheduling policy, it is scheduled; otherwise, it is not scheduled.

[0096] Customized duty and shift changes: After the duty template is configured, if the team wants to replace the person on duty on a certain day, the team leader can directly specify a custom person on duty on that day; or if person A in the team has something urgent to do on a certain day and wants to change shifts, the team leader can swap the duty dates of person A and person B to achieve the shift change effect. In both cases, there is no need to change the large duty template, only the data of a certain day and several days need to be adjusted.

[0097] Calculation index: It can be understood as the position of today's calculation; for example, if the duty cycle is 5 (rotating every 5 days), and the number of days on duty for each person is 2 (each person is on duty for 2 days), then the calculation index of the duty cycle is from 1 to 5. The calculation index of the number of days on duty is from 1 to 2. At 11:30 every night, there will be a scheduled task to update the calculation index. The update logic is: suppose today's duty cycle index is 3, that is, the third person is on duty, and the index of the number of days on duty is 1, that is, today has been on duty for one day, then after today's index is updated, the number of days on duty index +1 is 2, and the index of the duty cycle remains unchanged; tomorrow's index is updated, the index of the number of days on duty returns to 1, and the index of the duty cycle +1 is 4, and so on. That is, the index of the number of days on duty is updated first. After the index of the number of days on duty reaches the maximum value, the index of the number of days on duty is updated from the beginning, and the index of the duty cycle is +1. If the index of the duty cycle reaches the maximum value, the index of the duty cycle is updated from the beginning.

[0098] Duty history: At 11:30 every night, there will be a scheduled task to insert today's duty data into the duty history record. In this way, when viewing the team's duty calendar, you only need to calculate the data after today, and the data before today can be obtained from the history record.

[0099] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of various changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for calculating a duty system based on multiple teams and multiple applications, characterized in that: The following steps are involved: S1. Team configuration: First, it is necessary to define each duty team. Each team may have different professional fields and duty requirements; S2. Application classification: Classify the applications that require on-call support and determine different support levels and response time requirements based on the importance, complexity, and failure frequency of the applications; S3. Skill matching: Based on the skills and experience of team members, a skill library or matching algorithm is established to ensure that each duty task can be assigned to a team member with corresponding capabilities; S4. Duty Scheduling: Develop a scheduling algorithm that takes into account team members’ availability, preferences, and statutory rest time to generate a fair duty schedule; S5. Incident response process: Define a clear incident response process to ensure that on-duty personnel can quickly identify and classify incidents and take action according to established procedures.

2. The method for calculating a duty system based on multiple teams and multiple applications according to claim 1, characterized in that: In S1, the duty team includes team members, duty hours and scope of responsibilities.

3. The method for calculating a duty system based on multiple teams and multiple applications according to claim 1, characterized in that: In the S3, the steps for establishing a skill library are as follows: S3-10, Skill Record: Create a skills profile for each employee to record their skills and expertise; S3-11. Search and filter: Provide search and filter functions to quickly find employees with specific skills; S3-12, Skills Assessment: Regularly assess employees’ skills to ensure that the information in the skills database is up to date; S3-13, Skill Development: Identify skill gaps and provide employees with training and development opportunities to enhance the overall capabilities of the organization; S3-14. Reporting and analysis: Generate skills reports to help management analyze the skills status of the organization and provide a basis for strategic planning.

4. The method for calculating a duty system based on multiple teams and multiple applications according to claim 1, characterized in that: In said S3, the steps of the matching algorithm are as follows: S3-20, Team and Skills Database: The system first needs to build a database containing all team members and their skills, qualifications, availability, and preferences; S3-21, Task feature extraction: The system will extract relevant features from the duty tasks, which are used as input for the matching algorithm; S3-22, Algorithm design: Design matching algorithms based on the characteristics of the team and the task; S3-23, Matching process: The system matches the characteristics of the task with the skills and availability of team members. The algorithm will calculate according to the preset logic to find the best matching solution; S3-24. Result output: The matching algorithm will output a result indicating that the team members are matched with the corresponding tasks.

5. The method for calculating a duty system based on multiple teams and multiple applications according to claim 1, characterized in that: In S4, the scheduling algorithm is calculated when the person on duty is on duty. Since the duty configuration takes effect immediately on the same day, the initial calculation index position is the first. The calculation is based on the time range entered by the user. The data for today and later is calculated in real time, and the duty data before today depends on the historical record information.

6. The method for calculating a duty system based on multiple teams and multiple applications according to claim 1, characterized in that: In S5, the incident response process includes incident reporting, assessment, allocation, processing and tracking.

Images