CN117541198B - Comprehensive office cooperation management system - Google Patents

Comprehensive office cooperation management system Download PDF

Info

Publication number
CN117541198B
CN117541198B CN202410026612.1A CN202410026612A CN117541198B CN 117541198 B CN117541198 B CN 117541198B CN 202410026612 A CN202410026612 A CN 202410026612A CN 117541198 B CN117541198 B CN 117541198B
Authority
CN
China
Prior art keywords
task
time
module
subtasks
subtask
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202410026612.1A
Other languages
Chinese (zh)
Other versions
CN117541198A (en
Inventor
吴鹏
孙焕钦
彭陈诚
周宇
王霞
蒋登文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guizhou Door To Time Science & Technology Co ltd
Original Assignee
Guizhou Door To Time Science & Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guizhou Door To Time Science & Technology Co ltd filed Critical Guizhou Door To Time Science & Technology Co ltd
Priority to CN202410026612.1A priority Critical patent/CN117541198B/en
Publication of CN117541198A publication Critical patent/CN117541198A/en
Application granted granted Critical
Publication of CN117541198B publication Critical patent/CN117541198B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/162—Delete operations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311—Scheduling, planning or task assignment for a person or group
    • G06Q10/063114—Status monitoring or status determination for a person or group
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311—Scheduling, planning or task assignment for a person or group
    • G06Q10/063116—Schedule adjustment for a person or group
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0635—Risk analysis of enterprise or organisation activities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/101—Collaborative creation, e.g. joint development of products or services

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention relates to the technical field of office application, in particular to a comprehensive office cooperation management system. The system comprises a project management module, a plan management module, a task management module and a progress display module; the project management module is used for establishing a project group according to the project task, adding personnel associated with the project task to the project group, and determining an administrator and members of the project group; the project management module is used for acquiring task allocation of an administrator to project tasks, wherein the task allocation comprises responsible members of all matters in the project tasks, and the matters are sent to the corresponding members according to the task allocation; the task management module is used for acquiring the completion progress of matters of each member; and the progress display module is used for updating and displaying the total progress of the project task and the progress of each item according to the completion progress of the item of each member. Collaborative tasks for enterprise items can be managed.

Description

Comprehensive office cooperation management system
Technical Field
The invention relates to the technical field of office application, in particular to a comprehensive office cooperation management system.
Background
In large-scale projects of enterprises, task distribution in superior-to-subordinate arrangement and cross-department collaboration is generally involved, and the management of multiple persons, multiple departments and multiple tasks can greatly restrict the working efficiency and the effect if the management of data of the Internet is lacking. Currently, the existing project task management is mostly managed by using excel or a hand-drawn work schedule, but because a lot of uncertain factors exist in the task implementation process, the task cannot be implemented completely according to a preset plan, the upper level cannot conveniently determine the progress of the implementation of the lower level, and the lower level receives the upper level task and has delay. Greatly influencing the efficiency of the work. And because the practitioner and the manager and the different practitioner cannot effectively communicate, there may be some situations where work is repeatedly performed. Meanwhile, the updating of the schedule is complicated and complicated, so that the efficiency is reduced, and manpower and material resources are wasted.
Disclosure of Invention
The technical problem solved by the invention is to provide a comprehensive office cooperation management system which can manage cooperation tasks of enterprise projects.
The basic scheme provided by the invention is as follows: a comprehensive office cooperation management system comprises a project management module, a plan management module, a task management module and a progress display module;
The project management module is used for establishing a project group according to the project task, adding personnel associated with the project task to the project group, and determining an administrator and members of the project group;
the project management module is used for acquiring task allocation of an administrator to project tasks, wherein the task allocation comprises responsible members of all matters in the project tasks, and the matters are sent to the corresponding members according to the task allocation;
The task management module is used for acquiring the completion progress of matters of each member;
And the progress display module is used for updating and displaying the total progress of the project task and the progress of each item according to the completion progress of the item of each member.
The principle and the advantages of the invention are as follows: when the project stand is established, a project group is established, personnel participating in the project are added into the project group, internal communication can be carried out through the project group, and meanwhile, the manager and the member in the project group are determined. The administrator is the total responsible person of the project, and the members are the personnel participating in the project. And then, the administrator allocates matters to the tasks according to the content of the project, allocates the tasks and the matters to be completed which are responsible for all the personnel in the project group, and sends the allocated matters to the corresponding members in the project group. I.e. the individual persons in the project group are responsible for the events received by themselves. And then, managing the completion progress of the matters responsible for each member through a task management module, and updating and displaying the total progress of the project task according to the progress of the matters responsible for each member.
Compared with the prior art, by distributing project tasks, decomposing the tasks by an administrator, arranging matters responsible for each member, and tracking the progress of matters responsible for each member, the repeated work of the members can be avoided, and meanwhile, the progress of each matters and the overall progress of the overall task are clearly controlled.
Further, the plan management module comprises a task decomposition module, a time plan module and a task proportion module;
The task decomposition module is used for obtaining subtasks divided by an administrator for each item, wherein the item comprises a plurality of subtasks;
The time planning module is used for acquiring the planning time specified by the administrator for each subtask and binding the planning time with the subtask;
The task proportion module is used for acquiring task proportion of each subtask divided by an administrator.
When the manager distributes tasks, the matters responsible for one member are divided into a plurality of subtasks, and when the member distributes matters, each subtask is completed according to the arrangement. Meanwhile, the manager can set the planning time of each subtask according to the complexity degree of each subtask and the project experience of the member, namely the manager needs to complete the subtask within the specified planning time after the member starts the subtask, and the manager also needs to set the task proportion of the subtask according to the task quantity proportion of each subtask in matters. In this way, the matters which each member is responsible for are thinned, the planning time of each subtask is set, so that the member can know the time node when each subtask is completed when the matters are performed, and the member can know the task quantity of each subtask when the matters are completed by setting the task proportion of each subtask. By determining the time nodes and the task quantity, the time planning can be better performed by the members when each subtask is performed.
Further, the task management module comprises a file acquisition module and a progress update module;
The task acquisition module is used for acquiring completed subtasks submitted by the members, sending the completed subtasks to the manager and acquiring task assessment of the manager, wherein the task assessment comprises confirmation of completion and return modification, and when the task assessment is the return modification, the task assessment further comprises modification annotation;
and the progress updating module is used for updating the completion progress of the item according to the task proportion of the confirmed completed subtask when the task assessment of the completed subtask is confirmed to be completed, and adjusting the completion progress of the item according to the number of modification endorsements when the task assessment is returned to be modified.
And after the member completes the subtask, submitting the completed subtask to an administrator. The task acquisition module acquires the related file data of the subtasks completed by the members, and sends the related file data to an administrator, the administrator examines the completed subtasks, and if the examination passes, the task assessment is confirmed to be completed. If the administrator considers that the completed subtasks still need to be modified, annotating the parts needing to be modified and evaluating the given tasks as returning modification. When the task evaluation of the subtask is obtained, the progress updating module updates the completion progress of the matters according to the task proportion of the subtask if the task evaluation is confirmed to be completed, and adjusts the completion progress of the matters according to the number of modification endorsements if the current subtask cannot be judged to be completely completed if the task evaluation is returned to be modified. Since the number of modification annotations reflects the content to be modified, the more modification annotations, the more the content to be modified, and the lower the completion progress of the completion item when the modification annotations are more. In the scheme, the completion progress of the subtasks is adjusted by identifying the annotation quantity in the subtasks needing to be modified, but the whole progress is updated according to the specific gravity of the subtasks after the subtasks are completely completed. And determining the modification quantity of the subtasks according to the quantity of the endorsements, so that the completion progress of the subtasks when the subtasks are not completely completed is determined according to the modification quantity, and the progress management of matters responsible for each member is more accurate.
Further, the task obtaining module is further configured to obtain a task rating as a subtask that returns modification, and send the subtask to the manager, and obtain the task rating of the manager again until the task rating is confirmed to be completed;
And the progress updating module is also used for updating the completion progress of the matters according to the re-acquired task assessment.
And after the member finishes the subtask modification of which the task is rated as the return modification, the manager is required to review again, if the task rating is still the return modification after the review again, the modification is continued, and the item progress is updated until the task rating is confirmed to be finished.
After the subtask modification of the member's return modification is completed and submitted again, the administrator again performs an audit. And after rechecking, evaluating the completion progress of the updated matters according to the re-acquired task. If the task proportion of the subtask is not required to be modified, the completion progress of the subtask can be adjusted according to the task proportion of the subtask according to the overall progress after the subtask is completed, if the subtask still has parts to be modified, and only the parts to be modified are fewer than the parts to be modified before, the completion progress of the subtask is still adjusted according to the annotation quantity to be modified, and the subtask checking passing position is known. Through the mode, the completion progress of a matter can be updated every time a member submits a subtask, so that the overall progress of the task is controlled more accurately.
Further, the task management module also comprises a time management module;
And the time management module is used for recording the time from the start of each subtask to the assessment of the task as confirmation of completion, marking the time as actual use, judging whether the actual use exceeds the planned time, calculating the time difference between the actual use and the planned time when the actual use exceeds the planned time, and shortening the planned time of the subtask which is not started according to the specific gravity of the task which is not started in the matters and the time difference, wherein the shorter the planned time is the higher the specific gravity of the task of the subtask which is not started is.
Determining the actual time of the subtasks according to the starting time of each subtask and the task assessment as the time for confirming completion, when the actual time exceeds the planned time, indicating that the subtasks are not completed within the specified time, spending more time on the subtasks, ensuring that the overall completion time of matters has no larger deviation from the planned time, and adjusting the planned time of the following subtasks which are not started. And the time difference between the actual use and the planning time is calculated to obtain how much time is overtime for the member to finish the subtasks, and then the planning time of each subtask is shortened according to the task proportion occupied by the following subtasks and the overtime time difference, if the task proportion is higher, the shortening time is shorter, the task proportion is lower, and the shortening time is longer.
Further, the task management module further comprises a time analysis module, a task analysis module and a task scheduling module;
The time analysis module is used for identifying whether the time ratio of the shortened scheduled time of the subtasks to the scheduled time set by the administrator reaches a preset warning ratio;
The task analysis module is used for acquiring the number of the completed subtasks and all task evaluations of the completed subtasks in the matters when the time ratio of the subtasks reaches a preset guard ratio, calculating the task evaluations received by the subtasks as the average number of returned modifications, and marking the subtasks which are not started in the matters of the member as risk subtasks when the average number of the tasks is higher than a preset number threshold;
And the task scheduling module is used for calculating the total planned time and the total actual time of the subtasks completed by each member according to the completion progress of all the members in the project group and the current completed subtasks of each member, and scheduling the risk subtasks to the members with the total actual time smaller than the total planned time.
When the actual use of a member to complete a subtask exceeds the planning time, the planning time of a subtask which is not started later is shortened. When the preset guard ratio is reached, the scheduled time of the subtask is shortened to the minimum allowable scheduled time, and at the moment, whether the member can complete the subtask in the specified time is judged. There are two possibilities of shortening the planning time of the non-started subtasks, one is that the member has a low error rate, and in a certain subtask, because objective factors such as leave-on or other things are delayed, the time is longer, and the time is longer in the process of carrying out a certain subtask. Another possibility is that the member itself has a high error rate and most of the subtasks completed are returned modified, resulting in the actual use of most of the subtasks being greater than the scheduled time. When the time ratio of the subtasks reaches the alert ratio, the number of subtasks which are completed in the event by the member is obtained, the overall received task assessment is the number of returned modifications, the average number of times that the task assessment received by each subtask is returned modifications is calculated, if the average number of times is lower, the member is the first case, namely the member has a certain technical strength, delay is caused by objective factors, the returned modifications of the subtasks which are not started later are possibly lower, and the subtasks can be completed within the shortened planning time. If the average number of times is higher, the member is indicated to have more times of returning modification after completing the subtask, the subsequent subtasks which are not started still have higher risk of returning modification, and the returning modification can cause more delay time, and the risk of completing the subtask in the planning time is higher, so that the subtask is judged to be a risk subtask. When the risk subtask is judged to be the risk subtask, other members are required to accept the subtask, and the risk subtask is scheduled to the member with the total actual time less than the total planning time, namely the member with spare time for helping to process the risk subtask by calculating the total planning time and the total actual time of the completed subtask of all members in the project group.
Further, the task scheduling module comprises a time calculation module;
the time calculation module is used for calculating the total time difference between the total planning time and the total actual time of each member;
and the scheduling management module is used for scheduling the risk subtasks to the members according to the fact that whether the total time difference of the members is larger than the scheduled time after shortening the risk subtasks is identified, if yes, the members with the largest total time difference are marked as scheduling personnel, the subtasks, of which the scheduling personnel do not start, are identified, the subtasks with the closest scheduled time to the scheduled time after shortening the risk subtasks are scheduled to the members to which the risk subtasks belong, and the risk subtasks are scheduled to the scheduling personnel.
When task scheduling is carried out, if the total time difference of the members is larger than the scheduled time of the shortened risk subtasks, the task scheduling is directly carried out on the members. Since the member can complete the task before the specified time, it is determined that the risk subtask can be completed within the shortened planning time, and the risk subtask is directly scheduled to the member. If the time difference of no member is larger than the planned time after shortening the risk subtask, the angle is formed in a task exchange mode, the member with the largest total time difference is identified as a dispatcher, and the subtask with the shortest planned time after shortening the risk subtask and the planned time of the subtask which is not started by the dispatcher are obtained. The total actual use time of the dispatcher is smaller than the total planning time, so that the planning time of the subtasks of the dispatcher is not shortened, the planning time originally set by an administrator is kept, the risk subtasks are shortened, when the planning time after the shortening of the risk subtasks is similar to the subtask planning time of the dispatcher, the task quantity of the risk subtasks is actually higher than the task quantity of the subtasks of the dispatcher, the responsible members of the two tasks are exchanged, the processing capacity of the dispatcher is higher, the risk subtasks with larger task quantity can be processed in the same time, and the member processing capacity originally belonged to the risk subtasks is poorer, so that the subtasks with smaller task quantity are dispatched to the member for processing.
The system further comprises a resource management module, wherein the resource management module comprises a resource receiving module, an access recording module, an access analysis module and a resource judging module;
The resource receiving module is used for acquiring the shared file uploaded to the project group by the administrator and the member, storing the shared file in the shared space of the project group, and marking the member uploading the shared file as a resource uploading person of the shared file;
The access record module is used for acquiring access requests of the members to each shared file, generating an access record of the corresponding member to the accessed shared file and recording access time after the access requests of the members are acquired, and marking the members which initiate the access requests to the shared file as resource visitors of the shared file;
the access analysis module is used for counting the access times of each shared file according to the access record of each shared file and identifying the low-frequency shared file in the shared file according to the access times of the shared file;
the resource judging module is used for judging whether each low-frequency shared file is an effective file or not according to the resource uploading user of the low-frequency shared file and the resource accessing user of each access record at regular intervals, and deleting the low-frequency shared file from the shared space of the project group when the low-frequency shared file is not the effective resource file.
The members and administrators in the project group can upload related files required by the project into the shared space of the project group as shared files, and after uploading the shared files, the resource uploaders of the shared files are recorded. And then when a member accesses the shared file in the shared space, generating an access record and recording the access time. And then, the low-frequency shared files in the shared files, namely the shared files with fewer accessed times in the period, are identified according to the access records of the resource files in the shared space at regular intervals. And the resource judging module judges whether the shared file is effective or not according to the resource uploading user of the frequency shared file and the resource accessing user of each access record, and deletes the low-frequency shared file when judging that the shared file is ineffective.
In the prior art, for cleaning the group shared resource, cleaning is generally performed according to the time after uploading the shared file, for example, cleaning is performed after the shared file is uploaded for 90 days, and cleaning is performed after the shared file is uploaded for 14 days. However, for the shared file, some shared files are not used anymore after uploading for a certain time according to different uses of the shared file, and some shared resource files are used all the time. In the prior art, the cleaning mode according to the uploading time of the shared file can cause the long-term used shared file to be cleaned, the uploading needs to be performed again, and the shared file used only in a short period is stored for a long time, so that space resources are occupied. In the scheme, the access times of the shared files are identified regularly, namely the access frequency of the shared resources in each period is identified, and the low-frequency shared files with lower access frequency are obtained. The access times are identified in different periods, so that whether the shared file has a long-term use requirement or a short-term use requirement can be judged. And then, judging whether the resource is valid or not by the resource uploading user of the low-frequency shared file and the resource accessing user of each access record generated in the period, and deleting if the resource is not valid.
Further, the system also comprises a file sending module;
The access analysis module counts the total access times of all the shared files according to the access records of all the shared files in the period, generates an access threshold value in the period according to the total access times, and judges the shared files as low-frequency shared files when the access times of the shared files in the period are lower than the access threshold value;
The resource judging module is used for identifying the number of visitors accessing the low-frequency shared file in the period according to the resource visitors recorded by the low-frequency shared file, judging that the low-frequency shared file is not an effective file when the number of visitors is one, calculating the ratio of the number of visitors according to the number of visitors and the total number of people in the project group when the number of visitors is higher than one, and judging that the low-frequency shared file is not an effective file if the ratio of the number of visitors is lower than a preset ratio threshold;
And the file sending module is used for storing the local storage paths of the members and downloading the deleted low-frequency shared files to the local storage space according to the local storage paths of the resource visitors according to the resource visitors of the low-frequency shared files in the period after the low-frequency shared files are deleted from the shared space.
And generating an access threshold by identifying the total access times, and judging that the file is accessed at a low frequency when the access times of the file are lower than the access threshold. For low frequency access files, there may be a use that the file has shared in the near future, but different resource visitors have access less times, and possibly fewer people involved in the access, no longer having the sharing necessity. Therefore, when the number of people accessing the low-frequency shared file is one, namely, only one person accesses the low-frequency shared file in a period, the non-valid file can be directly judged. If the total number of the visitors in the project group is more than two, judging whether the visitors are effective files according to the total number ratio of the visitors in the project group, if the visitors are low, indicating that most members in the project group do not use the low-frequency shared files, and the visitors do not have the sharing requirement any more, judging the visitors to be the ineffective files. If the occupied area is high, the vast majority of members still use the device, but the use times are small, for example, each person only uses one time and two times, and the sharing requirement is still met. And then the deleted shared file is downloaded to the member accessing the resource in the period to enable the member to be used by itself, and the storage space of the shared space stored in the cloud is liberated.
Drawings
FIG. 1 is a logic block diagram of an embodiment of an integrated office collaboration management system in accordance with the present invention.
Detailed Description
The following is a further detailed description of the embodiments:
An example is substantially as shown in figure 1:
A comprehensive office cooperation management system comprises a project management module, a plan management module, a task management module and a progress display module.
The project management module is used for establishing a project group according to the project task, adding personnel associated with the project task to the project group, and determining the administrator and the member of the project group. Specifically, in this embodiment, a department responsible person determines a project task book, determines an administrator and a member of each project task through the project task book, performs text recognition on the project task book by uploading the project task book, and adds the administrator and the member in the project task book to a project group, so that functions which can be realized by the existing office communication software such as instant messaging, file sharing, video conference and the like can be performed in the project group.
The project management module is used for acquiring task allocation of an administrator to the project task, wherein the task allocation comprises responsible members of all matters in the project task, and the matters are sent to the corresponding members according to the task allocation. After receiving the project task, the administrator distributes the project task and distributes matters which are responsible for each person, for example, member A is responsible for XX area market research analysis, member B is responsible for XX county market research analysis, member C is responsible for evaluating the market plan, member D is responsible for researching competitors and the like. This assigns the item.
The plan management module comprises a task decomposition module, a time plan module and a task proportion module;
The task decomposition module is used for obtaining subtasks divided by an administrator for each item, wherein the item comprises a plurality of subtasks;
The time planning module is used for acquiring the planning time specified by the administrator for each subtask and binding the planning time with the subtask;
The task proportion module is used for acquiring task proportion of each subtask divided by an administrator.
Specifically, after assigning each member responsible item, the administrator performs subtask division on the item, for example, subtask 1: collecting a hand of data, subtask 2: collecting second hand data, sub-task 3: analysis data, sub-task 4: and (5) comprehensively researching results. Meanwhile, according to the task quantity of the subtasks, the planning time of each subtask is distributed, such as 8 hours of the planning time of the subtask 1, 10 hours of the planning time of the subtask 2 and the like. In addition, according to the task amount and the processing complexity of each task, the task proportion of the subtasks is distributed, for example, the task proportion of the subtask 1 is 20%, the task proportion of the subtask 2 is 30%, the task proportion of the subtask 3 is 40%, and the task proportion of the subtask 4 is 10%.
And the task management module is used for acquiring the completion progress of the matters of each member.
The task management module specifically comprises a file acquisition module and a progress update module.
The task acquisition module is used for acquiring completed subtasks submitted by the members, sending the completed subtasks to the manager and acquiring task assessment of the manager, wherein the task assessment comprises confirmation of completion and return modification, and when the task assessment is the return modification, the task assessment further comprises modification annotation. Specifically, after the member completes the subtask, the member uploads the relevant file of the subtask to the task group, and the administrator can review and annotate the relevant file of the subtask uploaded by the member.
And the progress updating module is used for updating the completion progress of the item according to the task proportion of the confirmed completed subtask when the task assessment of the completed subtask is confirmed to be completed, and adjusting the completion progress of the item according to the number of modification endorsements when the task assessment is returned to be modified. And after the administrator performs the auditing of the subtasks, submitting the task assessment results of the subtasks, if the subtasks are not required to be modified, the assessment results are confirmed to be completed, and if the subtasks are required to be modified, the assessment results are returned to be modified. When the assessment result is that the completion is confirmed, the completion progress of matters responsible for each member is updated according to the task proportion of the subtask, if the task proportion of the subtask 1 is 20%, the task proportion of the subtask 2 is 10%, after the task 1 confirms the completion, the completion progress of matters of the member is updated to be 20%, after the task 2 is completed, the completion progress of matters of the member is updated to be 30%, and so on. If the assessment result of the member subtask 1 is the return modification, the number of the endorsements in the file is identified, and the completion progress is adjusted according to the number of the endorsements, in this embodiment, each 1 endorsement, the completion progress is reduced by 0.5%. For example, the subtask 1 of the member has a task weight of 20%, the submitted related file task is rated as a return modification, and 10 comments therein, the completion progress of the member's matter is updated to 15%.
And the task acquisition module is also used for acquiring the task assessment as a subtask which is returned to be modified and sending the subtask to the manager, and acquiring the task assessment of the manager again until the task assessment is confirmed to be completed. After the subtask modification of the member's return modification is completed and submitted again, the administrator again performs an audit. And the progress updating module is also used for updating the completion progress of the matters according to the re-acquired task assessment. And after rechecking, evaluating the completion progress of the updated matters according to the re-acquired task. If the task proportion of the subtask is not required to be modified, the completion progress of the subtask can be adjusted according to the task proportion of the subtask according to the overall progress after the subtask is completed, if the subtask still has parts to be modified, and only the parts to be modified are fewer than the parts to be modified before, the completion progress of the subtask is still adjusted according to the annotation quantity to be modified, and the subtask checking passing position is known. Through the mode, the completion progress of a matter can be updated every time a member submits a subtask, so that the overall progress of the task is controlled more accurately. For example, the number of original annotations is 10, the item progress of the member is 15%, if the member is re-modified and is judged to confirm completion, the update progress is 20%, and if the number of re-modified annotations is 5, the update progress is 17.5%, and the member is returned to continue modification until the task assessment is confirmed completion.
The task management module also includes a time management module.
And the time management module is used for recording the time from the start of each subtask to the assessment of the task as confirmation of completion, marking the time as actual use, judging whether the actual use exceeds the planned time, calculating the time difference between the actual use and the planned time when the actual use exceeds the planned time, and shortening the planned time of the subtask which is not started according to the specific gravity of the task which is not started in the matters and the time difference, wherein the shorter the planned time is the higher the specific gravity of the task of the subtask which is not started is.
When the member starts to conduct the subtask, the starting time is recorded, and when the task assessment is confirmed to be completed, the completion time is recorded, so that the actual time is calculated according to the working time. Judging whether the actual use exceeds the planning time, and when the actual use exceeds the planning time, shortening the planning time of the sub-tasks which are not started according to the task proportion of the sub-tasks which are not started in the matters and the calculated exceeding time difference. For example, when the subtask 1 of a member overtakes for 3 hours, the subtask not started by the member comprises a subtask 2 and a subtask 3, the planning time of the subtask 2 is 10 hours, the task proportion of the subtask 2 is 40%, the planning time of the subtask 3 is 8 hours, the task proportion of the subtask 3 is 20%, and the planning time of the subtask 2 is shortened by 1 hour according to the ratio of the task proportions of the subtask 3 and the subtask 2, and the planning time of the subtask 3 is shortened by 2 hours.
Example two
The difference between the present embodiment and the first embodiment is that the task management module in this embodiment further includes a time analysis module, a task analysis module, and a task scheduling module.
And the time analysis module is used for identifying whether the time ratio of the shortened scheduled time of the subtasks to the scheduled time set by the administrator reaches a preset warning ratio. For example, if the scheduled time set by the administrator of the sub-task 3 is 10 hours and the shortened scheduled time is 8 hours, the ratio of the shortened scheduled time to the original scheduled time is 0.8. Meanwhile, the guard ratio is preset, in this embodiment, the guard ratio is 0.7, that is, when the shortened planning time reaches 70% of the original planning time, the guard ratio is reached.
The task analysis module is used for acquiring the number of the completed subtasks and all task evaluations of the completed subtasks in the event when the time ratio of the subtasks reaches a preset guard ratio, calculating the task evaluations received by the subtasks as the average number of returned modifications, and marking the subtasks which are not started in the event of the member as risk subtasks when the average number of the received task evaluations is higher than a preset number threshold.
Specifically, when the time ratio of the existing subtasks reaches the guard ratio, judging that the task assessment received by the subtasks of the member to which the subtasks belong in the matters is the average number of returned modifications. For example, the member has completed two subtasks, the number of return modifications is 1, and the average number of return modifications is 0.5. Comparing the average times with a preset times threshold, wherein the times threshold in the embodiment is 1.5 times, namely when the average times of the return modification exceeds 1.5 times, judging that the times threshold is exceeded, and marking the sub-tasks which are not started in the member matters as non-risk sub-tasks.
And the task scheduling module is used for calculating the total planned time and the total actual time of the subtasks completed by each member according to the completion progress of all the members in the project group and the current completed subtasks of each member, and scheduling the risk subtasks to the members with the total actual time smaller than the total planned time. For example, the subtasks completed by a member include task 1, task 2 and task 3, the planning time of task 1 is not 8 hours, the planning time of task 2 is 10 hours, the planning time of task 2 is 8 hours, the planning time of task 3 is 6 hours, the planning time of task 3 is 5 hours, the total planning time is 24 hours, the total actual time is 20 hours, and the total actual time is smaller than the total planning time. The risk subtask may be scheduled to the member.
When the actual use of a member to complete a subtask exceeds the planning time, the planning time of a subtask which is not started later is shortened. When the preset guard ratio is reached, the scheduled time of the subtask is shortened to the minimum allowable scheduled time, and at the moment, whether the member can complete the subtask in the specified time is judged. There are two possibilities of shortening the planning time of the non-started subtasks, one is that the member has a low error rate, and in a certain subtask, because objective factors such as leave-on or other things are delayed, the time is longer, and the time is longer in the process of carrying out a certain subtask. Another possibility is that the member itself has a high error rate and most of the subtasks completed are returned modified, resulting in the actual use of most of the subtasks being greater than the scheduled time. When the time ratio of the subtasks reaches the alert ratio, the number of subtasks which are completed in the event by the member is obtained, the overall received task assessment is the number of returned modifications, the average number of times that the task assessment received by each subtask is returned modifications is calculated, if the average number of times is lower, the member is the first case, namely the member has a certain technical strength, delay is caused by objective factors, the returned modifications of the subtasks which are not started later are possibly lower, and the subtasks can be completed within the shortened planning time. If the average number of times is higher, the member is indicated to have more times of returning modification after completing the subtask, the subsequent subtasks which are not started still have higher risk of returning modification, and the returning modification can cause more delay time, and the risk of completing the subtask in the planning time is higher, so that the subtask is judged to be a risk subtask. When the risk subtask is judged to be the risk subtask, other members are required to accept the subtask, and the risk subtask is scheduled to the member with the total actual time less than the total planning time, namely the member with spare time for helping to process the risk subtask by calculating the total planning time and the total actual time of the completed subtask of all members in the project group.
The task scheduling module comprises a time calculation module and a scheduling management module;
And the time calculation module is used for calculating the total time difference between the total planned time and the total actual time of each member. In performing scheduling of risk subtasks, first, the total time difference between the overall planned time and the overall actual time of each member at the site is calculated. If the total planned time is 24 hours, the total actual time is 20 hours, and the total time difference is 4 hours.
And the scheduling management module is used for scheduling the risk subtasks to the members according to the fact that whether the total time difference of the members is larger than the scheduled time after shortening the risk subtasks is identified, if yes, the members with the largest total time difference are marked as scheduling personnel, the subtasks, of which the scheduling personnel do not start, are identified, the subtasks with the closest scheduled time to the scheduled time after shortening the risk subtasks are scheduled to the members to which the risk subtasks belong, and the risk subtasks are scheduled to the scheduling personnel. Assuming that the planned time after shortening the risk subtask is 4 hours, the total time difference of the members is 6 hours, and the risk subtask can be directly scheduled to the members. If the total time difference of no member is greater than 4 hours, firstly selecting the member with the largest total time difference as a dispatching member, and then selecting the subtask with the closest planning time to the risk subtask from the subtask which is not started by the dispatching member, wherein the subtask which is not started comprises a subtask 5 and a subtask 6 in the dispatching member, the planning time of the subtask 5 is 3 hours, the planning time of the subtask 6 is 4 hours, dispatching the subtask 6 of the dispatching personnel to the member which the risk subtask originally belongs to, and dispatching the risk subtask to the dispatching personnel. At this time, since the task is completed in advance before the task is scheduled, there is no timeout, and thus the scheduled time of the subtask 6 is maintained at the scheduled time originally set by the administrator. The risk subtask is to shorten the planning time, which is not 4 hours. When the scheduled time of the shortened risk subtask is similar to the scheduled time of the subtask of the dispatcher, the task amount of the risk subtask is actually higher than the task amount of the subtask 6 of the dispatcher, the responsible members of the two tasks are exchanged, the dispatcher has stronger processing capacity and can process the risk subtask with larger task amount in the same time, and the member processing capacity of the risk subtask originally belongs to the risk subtask is poorer, so that the subtask 6 with smaller task amount is dispatched to the member for processing.
Example III
The difference between the present embodiment and the first embodiment is that in this embodiment, the system further includes a resource management module, where the resource management module includes a resource receiving module, an access recording module, an access analysis module, a resource judging module, and a file sending module.
The resource receiving module is used for acquiring the shared file uploaded to the project group by the administrator and the member, storing the shared file in the shared space of the project group, and marking the member uploading the shared file as a resource uploading person of the shared file. Specifically, by setting a cloud database, after the project group is established, the shared space of the project group is distributed from the cloud database. The member can upload the local files to the shared space of the cloud database in the project group, and records the uploaders of the shared files.
And the access record module is used for acquiring the access requests of the members to each shared file, generating an access record of the corresponding member to the accessed shared file once after the access requests of the members are acquired, recording the access time, and marking the members which initiate the access requests to the shared file as resource visitors of the shared file. After personnel access, recording access records and access time of each shared file.
And the access analysis module is used for counting the access times of each shared file according to the access record of each shared file and identifying the low-frequency shared file in the shared file according to the access times of the shared file. Specifically, according to the access records of all the shared files in the period, the total access times of all the shared files are counted, and according to the total access times, an access threshold in the period is generated, and when the access times of the shared files in the period are lower than the access threshold, the shared files are judged to be low-frequency shared files.
The resource judging module is used for judging whether each low-frequency shared file is an effective file or not according to the resource uploading user of the low-frequency shared file and the resource accessing user of each access record at regular intervals, and deleting the low-frequency shared file from the shared space of the project group when the low-frequency shared file is not the effective resource file. Specifically, the resource judging module identifies the number of visitors accessing the low-frequency shared file in the period according to the resource visitors recorded by the low-frequency shared file, judges that the low-frequency shared file is an invalid file when the number of visitors is one, calculates the ratio of the number of visitors according to the number of visitors and the total number of people in the project group when the number of visitors is higher than one, and judges that the low-frequency shared file is an invalid file if the ratio of the number of visitors is lower than a preset ratio threshold.
The members and administrators in the project group can upload related files required by the project into the shared space of the project group as shared files, and after uploading the shared files, the resource uploaders of the shared files are recorded. And then when a member accesses the shared file in the shared space, generating an access record and recording the access time. And then, the low-frequency shared files in the shared files, namely the shared files with fewer accessed times in the period, are identified according to the access records of the resource files in the shared space at regular intervals. And the resource judging module judges whether the shared file is effective or not according to the resource uploading user of the frequency shared file and the resource accessing user of each access record, and deletes the low-frequency shared file when judging that the shared file is ineffective.
And the file sending module is used for storing the local storage paths of the members and downloading the deleted low-frequency shared files to the local storage space according to the local storage paths of the resource visitors according to the resource visitors of the low-frequency shared files in the period after the low-frequency shared files are deleted from the shared space. Specifically, the local storage path of the member is recorded, and after the shared resource is deleted from the cloud database, the member's local storage path which has been accessed recently is directly downloaded.
In the prior art, for cleaning the group shared resource, cleaning is generally performed according to the time after uploading the shared file, for example, cleaning is performed after the shared file is uploaded for 90 days, and cleaning is performed after the shared file is uploaded for 14 days. However, for the shared file, some shared files are not used anymore after uploading for a certain time according to different uses of the shared file, and some shared resource files are used all the time. In the prior art, the cleaning mode according to the uploading time of the shared file can cause the long-term used shared file to be cleaned, the uploading needs to be performed again, and the shared file used only in a short period is stored for a long time, so that space resources are occupied. In the scheme, the access times of the shared files are identified regularly, namely the access frequency of the shared resources in each period is identified, and the low-frequency shared files with lower access frequency are obtained. The access times are identified in different periods, so that whether the shared file has a long-term use requirement or a short-term use requirement can be judged. And then, judging whether the resource is valid or not by the resource uploading user of the low-frequency shared file and the resource accessing user of each access record generated in the period, and deleting if the resource is not valid.
And generating an access threshold by identifying the total access times, and judging that the file is accessed at a low frequency when the access times of the file are lower than the access threshold. For low frequency access files, there may be a use that the file has shared in the near future, but different resource visitors have access less times, and possibly fewer people involved in the access, no longer having the sharing necessity. Therefore, when the number of people accessing the low-frequency shared file is one, namely, only one person accesses the low-frequency shared file in a period, the non-valid file can be directly judged. If the total number of the visitors in the project group is more than two, judging whether the visitors are effective files according to the total number ratio of the visitors in the project group, if the visitors are low, indicating that most members in the project group do not use the low-frequency shared files, and the visitors do not have the sharing requirement any more, judging the visitors to be the ineffective files. If the occupied area is high, the vast majority of members still use the device, but the use times are small, for example, each person only uses one time and two times, and the sharing requirement is still met. And then the deleted shared file is downloaded to the member accessing the resource in the period to enable the member to be used by itself, and the storage space of the shared space stored in the cloud is liberated.
The foregoing is merely exemplary of the present application, and specific structures and features well known in the art will not be described in detail herein, so that those skilled in the art will be aware of all the prior art to which the present application pertains, and will be able to ascertain the general knowledge of the technical field in the application or prior art, and will not be able to ascertain the general knowledge of the technical field in the prior art, without using the prior art, to practice the present application, with the aid of the present application, to ascertain the general knowledge of the same general knowledge of the technical field in general purpose. It should be noted that modifications and improvements can be made by those skilled in the art without departing from the structure of the present application, and these should also be considered as the scope of the present application, which does not affect the effect of the implementation of the present application and the utility of the patent. The protection scope of the present application is subject to the content of the claims, and the description of the specific embodiments and the like in the specification can be used for explaining the content of the claims.

Claims (2)

1. A comprehensive office cooperation management system is characterized in that: the system comprises a project management module, a plan management module, a task management module and a progress display module;
The project management module is used for establishing a project group according to the project task, adding personnel associated with the project task to the project group, and determining an administrator and members of the project group;
the project management module is used for acquiring task allocation of an administrator to project tasks, wherein the task allocation comprises responsible members of all matters in the project tasks, and the matters are sent to the corresponding members according to the task allocation;
The task management module is used for acquiring the completion progress of matters of each member;
The progress display module is used for updating and displaying the total progress of the project task and the progress of each item according to the completion progress of the item of each member;
the system also comprises a resource management module, wherein the resource management module comprises a resource receiving module, an access recording module, an access analysis module and a resource judging module;
The resource receiving module is used for acquiring the shared file uploaded to the project group by the administrator and the member, storing the shared file in the shared space of the project group, and marking the member uploading the shared file as a resource uploading person of the shared file;
The access record module is used for acquiring access requests of the members to each shared file, generating an access record of the corresponding member to the accessed shared file and recording access time after the access requests of the members are acquired, and marking the members which initiate the access requests to the shared file as resource visitors of the shared file;
the access analysis module is used for counting the access times of each shared file according to the access record of each shared file and identifying the low-frequency shared file in the shared file according to the access times of the shared file;
The resource judging module is used for judging whether each low-frequency shared file is an effective file or not according to the resource uploading person of the low-frequency shared file and the resource accessing person accessing the record each time in the period at regular intervals, and deleting the low-frequency shared file from the shared space of the project group when the low-frequency shared file is not the effective resource file;
the plan management module comprises a task decomposition module, a time plan module and a task proportion module;
The task decomposition module is used for obtaining subtasks divided by an administrator for each item, wherein the item comprises a plurality of subtasks;
The time planning module is used for acquiring the planning time specified by the administrator for each subtask and binding the planning time with the subtask;
The task proportion module is used for acquiring task proportion of division of each subtask by an administrator;
the task management module comprises a file acquisition module and a progress update module;
The task acquisition module is used for acquiring completed subtasks submitted by the members, sending the completed subtasks to the manager and acquiring task assessment of the manager, wherein the task assessment comprises confirmation of completion and return modification, and when the task assessment is the return modification, the task assessment further comprises modification annotation;
The progress updating module is used for updating the completion progress of the item according to the task proportion of the confirmed completed subtask when the task assessment of the completed subtask is confirmed to be completed, and adjusting the completion progress of the item according to the number of modification endorsements when the task assessment is returned to be modified;
the task acquisition module is also used for acquiring the task assessment as a subtask which returns to modification and sending the subtask to the manager, and acquiring the task assessment of the manager again until the task assessment is confirmed to be completed;
The progress updating module is also used for updating the completion progress of the matters according to the re-acquired task assessment;
The task management module also comprises a time management module;
The time management module is used for recording the time from the start of each subtask to the assessment of the task as confirmation of completion, marking the time as actual use, judging whether the actual use exceeds the planned time, calculating the time difference between the actual use and the planned time when the actual use exceeds the planned time, and shortening the planned time of the subtask which is not started according to the task proportion of the subtask which is not started in the matters and the time difference, wherein the higher the task proportion of the subtask which is not started is, the shorter the planned time is;
the task management module further comprises a time analysis module, a task analysis module and a task scheduling module;
The time analysis module is used for identifying whether the time ratio of the shortened scheduled time of the subtasks to the scheduled time set by the administrator reaches a preset warning ratio;
The task analysis module is used for acquiring the number of the completed subtasks and all task evaluations of the completed subtasks in the matters when the time ratio of the subtasks reaches a preset guard ratio, calculating the task evaluations received by the subtasks as the average number of returned modifications, and marking the subtasks which are not started in the matters of the member as risk subtasks when the average number of the tasks is higher than a preset number threshold;
The task scheduling module is used for calculating the total planned time and the total actual time of the subtasks completed by each member according to the completion progress of all the members in the project group and the current completed subtasks of each member, and scheduling the risk subtasks to the members with the total actual time smaller than the total planned time;
the task scheduling module comprises a time calculation module and a scheduling management module;
the time calculation module is used for calculating the total time difference between the total planning time and the total actual time of each member;
and the scheduling management module is used for scheduling the risk subtasks to the members according to the fact that whether the total time difference of the members is larger than the scheduled time after shortening the risk subtasks is identified, if yes, the members with the largest total time difference are marked as scheduling personnel, the subtasks, of which the scheduling personnel do not start, are identified, the subtasks with the closest scheduled time to the scheduled time after shortening the risk subtasks are scheduled to the members to which the risk subtasks belong, and the risk subtasks are scheduled to the scheduling personnel.
2. A comprehensive office collaboration management system as claimed in claim 1 wherein: the access analysis module comprises a file definition module, and the resource judgment module comprises an effective analysis module;
The file definition module is used for counting the total access times of all the shared files according to the access records of all the shared files in the period, generating an access threshold value in the period according to the total access times, and judging the shared files as low-frequency shared files when the access times of the shared files in the period are lower than the access threshold value;
The effective analysis module is used for identifying the number of visitors accessing the low-frequency shared file in the period according to the resource visitors recorded by the low-frequency shared file, judging that the low-frequency shared file is not an effective file when the number of visitors is one, calculating the ratio of the number of visitors according to the number of visitors and the total number of people in the project group when the number of visitors is higher than one, and judging that the low-frequency shared file is not an effective file if the ratio of the number of visitors is lower than a preset ratio threshold;
And the file sending module is used for storing the local storage paths of the members and downloading the deleted low-frequency shared files to the local storage space according to the local storage paths of the resource visitors according to the resource visitors of the low-frequency shared files in the period after the low-frequency shared files are deleted from the shared space.
CN202410026612.1A 2024-01-09 2024-01-09 Comprehensive office cooperation management system Active CN117541198B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410026612.1A CN117541198B (en) 2024-01-09 2024-01-09 Comprehensive office cooperation management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410026612.1A CN117541198B (en) 2024-01-09 2024-01-09 Comprehensive office cooperation management system

Publications (2)

Publication Number Publication Date
CN117541198A CN117541198A (en) 2024-02-09
CN117541198B true CN117541198B (en) 2024-04-30

Family

ID=89790333

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410026612.1A Active CN117541198B (en) 2024-01-09 2024-01-09 Comprehensive office cooperation management system

Country Status (1)

Country Link
CN (1) CN117541198B (en)

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104463558A (en) * 2014-11-13 2015-03-25 深圳市玖昔物联科技发展有限公司 Networked work cooperative system and method
CN106296125A (en) * 2016-08-10 2017-01-04 安徽喜悦信息科技有限公司 A kind of computer automation office system avoiding overtime work
CN107135257A (en) * 2017-04-28 2017-09-05 东方网力科技股份有限公司 Task is distributed in a kind of node cluster method, node and system
CN108667895A (en) * 2018-03-16 2018-10-16 南方科技大学 File sharing method, server based on Quick Response Code and terminal device
CN110135719A (en) * 2019-05-08 2019-08-16 重庆八戒电子商务有限公司 Cooperative system and method are remotely researched and developed in a kind of internet
CN112751746A (en) * 2020-12-28 2021-05-04 北京达佳互联信息技术有限公司 Task processing method and device and electronic equipment
CN113099729A (en) * 2018-10-26 2021-07-09 陶氏环球技术有限责任公司 Deep reinforcement learning for production scheduling
CN113407161A (en) * 2021-06-04 2021-09-17 中船重工奥蓝托无锡软件技术有限公司 Complex equipment-oriented collaborative research and development management system
CN113421058A (en) * 2021-06-22 2021-09-21 浙江工贸职业技术学院 Public management system
CN113537568A (en) * 2021-06-18 2021-10-22 中国电力科学研究院有限公司 Method and system for determining scheduling plan of steel hot rolling production
CN115841310A (en) * 2022-12-29 2023-03-24 奇安信网神信息技术(北京)股份有限公司 Construction method of plan flow model, event processing method and device
CN116983617A (en) * 2023-09-25 2023-11-03 深圳云天畅想信息科技有限公司 Cross-cluster resource scheduling method, computer device and storage medium
CN117118742A (en) * 2023-10-16 2023-11-24 思创数码科技股份有限公司 Government affair data operation method and system based on access frequency monitoring
CN117196530A (en) * 2023-09-20 2023-12-08 数钥网络技术(杭州)有限公司 Digital intelligent scheduling method and system for software project set and human resource pool
CN117333026A (en) * 2023-11-21 2024-01-02 国网河南省电力公司开封供电公司 Risk identification method based on energy big data
CN117350487A (en) * 2023-10-08 2024-01-05 河南星际项目管理有限公司 Engineering project progress management system and method based on big data

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130231971A1 (en) * 2011-08-23 2013-09-05 Judy Bishop Legal project management system and method

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104463558A (en) * 2014-11-13 2015-03-25 深圳市玖昔物联科技发展有限公司 Networked work cooperative system and method
CN106296125A (en) * 2016-08-10 2017-01-04 安徽喜悦信息科技有限公司 A kind of computer automation office system avoiding overtime work
CN107135257A (en) * 2017-04-28 2017-09-05 东方网力科技股份有限公司 Task is distributed in a kind of node cluster method, node and system
CN108667895A (en) * 2018-03-16 2018-10-16 南方科技大学 File sharing method, server based on Quick Response Code and terminal device
CN113099729A (en) * 2018-10-26 2021-07-09 陶氏环球技术有限责任公司 Deep reinforcement learning for production scheduling
CN110135719A (en) * 2019-05-08 2019-08-16 重庆八戒电子商务有限公司 Cooperative system and method are remotely researched and developed in a kind of internet
CN112751746A (en) * 2020-12-28 2021-05-04 北京达佳互联信息技术有限公司 Task processing method and device and electronic equipment
CN113407161A (en) * 2021-06-04 2021-09-17 中船重工奥蓝托无锡软件技术有限公司 Complex equipment-oriented collaborative research and development management system
CN113537568A (en) * 2021-06-18 2021-10-22 中国电力科学研究院有限公司 Method and system for determining scheduling plan of steel hot rolling production
CN113421058A (en) * 2021-06-22 2021-09-21 浙江工贸职业技术学院 Public management system
CN115841310A (en) * 2022-12-29 2023-03-24 奇安信网神信息技术(北京)股份有限公司 Construction method of plan flow model, event processing method and device
CN117196530A (en) * 2023-09-20 2023-12-08 数钥网络技术(杭州)有限公司 Digital intelligent scheduling method and system for software project set and human resource pool
CN116983617A (en) * 2023-09-25 2023-11-03 深圳云天畅想信息科技有限公司 Cross-cluster resource scheduling method, computer device and storage medium
CN117350487A (en) * 2023-10-08 2024-01-05 河南星际项目管理有限公司 Engineering project progress management system and method based on big data
CN117118742A (en) * 2023-10-16 2023-11-24 思创数码科技股份有限公司 Government affair data operation method and system based on access frequency monitoring
CN117333026A (en) * 2023-11-21 2024-01-02 国网河南省电力公司开封供电公司 Risk identification method based on energy big data

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
Multi-mode resource-constrained project scheduling problems with non-preemptive activity splitting;Junzilan Cheng 等;《Computers & Operations Research》;20140509;第53卷;第275-287页 *
公路工程设计过程的优化理论框架及关键技术研究;张志强;《中国博士学位论文全文数据库 工程科技Ⅱ辑》;20130215(第2期);第C034-7页 *
基于知识组元的钢铁生产多扰动优化调度知识挖掘及其系统研究;陈小武;《中国博士学位论文全文数据库 工程科技Ⅰ辑》;20230315(第3期);第B023-3页 *
资源受限装备试验鉴定任务调度建模与决策;崔荣伟 等;《舰船电子工程》;20230620;第43卷(第6期);第90-93页 *

Also Published As

Publication number Publication date
CN117541198A (en) 2024-02-09

Similar Documents

Publication Publication Date Title
EP1681634A1 (en) Method and system for tracking changes in a document
US7698248B2 (en) Method and system for auditing processes and projects for process improvement
US20110072436A1 (en) Resource optimization for real-time task assignment in multi-process environments
CN103577915A (en) Task allocation management system and method
CN111027944A (en) Human resource management system
CN111192021A (en) OA document approval implementation method and system
Costello RACI—Getting Projects" Unstuck"
Ham et al. Optimal BIM staffing in construction projects using a queueing model
JP4913647B2 (en) Mental health management device
CN113361816A (en) One set of customer service staff scheduling system
US20030101085A1 (en) Method and system for vendor communication
Margatama Employee self service-based human resources information system development and implementation. Case study: BCP Indonesia
CN115471200A (en) Cloud computing-based human resource data management system, method and device
US10121111B2 (en) Coordinating contending resources
Song et al. Optimal appointment rule design in an outpatient department
CN117541198B (en) Comprehensive office cooperation management system
CN1581180A (en) Dynamic management and control system and method for staff attendance
JP4913648B2 (en) Mental health management device
JP5812911B2 (en) Workflow management system, workflow management method, and workflow management program
RU59860U1 (en) AUTOMATED SYSTEM FOR COLLECTING AND PROCESSING DATA ON COMPANY PERSONNEL
CN117196530A (en) Digital intelligent scheduling method and system for software project set and human resource pool
US20060026053A1 (en) Goal tender system and method
Djedović et al. Optimization of the business processes via automatic integration with the document management system
CN112633834A (en) Method and system for project declaration demand analysis
JP2021096514A (en) Information processing device and information processing method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant