JP2018106673A - Computer system, management method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce an occurrence of mismanagement of an upper level performance relevant item and a lower level performance relevant item, to save effort of managing the same and to facilitate understanding of a relation between the same.SOLUTION: In a computer system, the following information is input into a management server: a work item C as an example of upper level performance relevant items; an allowable time frame of the work item C; a planned item E as an example of a lower level performance relevant items, which is related to the work item C and imposes a time constraint in the allowable time frame of the work item C; and the time constraint imposed by the planned item E. Then, the computer system unifies management of the work item and the planned item by causing a database 5 to store both of the input performance relevant items with the same associated with each other using a path.SELECTED DRAWING: Figure 2

Description

  The present invention manages, for example, performance-related items related to items to be performed by the user, such as a user's schedule, work, and plan, and more specifically, a computer system and a management method capable of managing the performance-related items. And program.

  Conventionally, there has been a calendar display method and a display device as disclosed in Patent Document 1, for example, for performing schedule management.

JP-A-9-73434

  However, according to the method disclosed in Patent Document 1, a schedule (schedule) is input and displayed on a calendar for management. Therefore, although the schedule (plan) could be managed, the work could not be managed. Therefore, in order to manage work, a work management device must be prepared separately from the calendar display device.

  However, when the schedule is managed by the calendar display device and the work is managed by the work management device, the user is forced to operate both devices to manage, and the management becomes complicated. There is. As a result, when the emphasis is placed on one management, the other management is neglected. Moreover, there is a drawback that the relationship between work and schedule cannot be grasped.

  These shortcomings are managed separately without coordination between the work (for example, “request for patent application”) and the schedule related to the work (for example, “schedule for a meeting with a patent attorney from 2:00 pm tomorrow”). Due to being. In other words, the upper performance related items (for example, work) related to the items to be performed by the user and the lower performance related items (for example, associated with performing the tasks) related to the items to be performed related to the higher performance related items. This is due to the fact that they are managed separately without being linked.

  The present invention has been devised in view of the actual situation, and its purpose is to reduce omissions in management and troubles between higher performance related items and lower performance related items, as well as higher performance related items and lower performance related items. It is to make it easier to understand the relationship with the matter.

  In the following, the specific contents of the embodiment corresponding to each means for solving the problem are shown in parentheses.

The computer system of the present invention includes a storage means (for example, the database 5) capable of storing performance-related items (for example, plan items, tasks, schedules) related to items to be performed by the user and the execution time thereof,
The work items (for example, preparation of the specification in FIG. 1) included in the higher-level performance-related items (for example, plan items, tasks) and the lower-level performance-related items (for example, schedules) necessary to specifically execute the job items ) (For example, the fifth meeting schedule 25 of the meeting with the patent attorney in FIG. 1) can be input, and the execution time of the work item and the user's constraint that is the execution time of the schedule item An input means (for example, the input operation unit 38) capable of inputting a period;
In a state where the work item and its execution time are stored in the storage unit, it is determined whether the constraint period of the scheduled item input by the input unit is consistent with the execution time of the work item. Determining means (for example, determining means 72 in FIG. 2),
Storage means for controlling the storage means, the storage means for storing the input schedule item and its restraint period in the storage means, and the input schedule item and a work item that is related to the higher level execution. And a processing unit (for example, the processing unit 73, CPU 30, S50 in FIG. 2) that is stored in the storage unit in cooperation with each other so that they can be managed in a unified manner,
The processing means includes
When the determination means determines that they are not consistent, the storage process is prohibited (for example, NO in S46, S43),
In a state in which the scheduled items input as the user's own performance-related items and the work items that are the immediate higher-level performance-related items are linked and stored in the storage means, the work items are directly related to the higher-level performance-related items. The scheduled items as the performance-related items of the user who is the same person as the user and the constraint period thereof are newly inputted, and Even when the newly input constraint period overlaps, the storage process is prohibited (for example, NO in S42, S43).

  According to the present invention, the work items included in the high-level performance-related items to be performed and the scheduled items as the low-level performance-related items necessary for concretely performing the work items are linked so as to be managed in an integrated manner. Therefore, the omission of management of work items and scheduled items and the labor of management are reduced, and the relationship between the work items and the scheduled items can be easily grasped.

It is a figure which shows the structure of the whole system. It is a functional block diagram. (A) is a block diagram showing a control circuit of the client terminal and the management server, (b) is a flowchart showing a main routine program of the client terminal and the management server, and (c) is a data editing process and data editing. It is a flowchart which shows the subroutine program of a corresponding | compatible process. (A) is a flowchart which shows the subroutine program of plan input processing, (b) is a flowchart which shows the subroutine program of work input processing. (A) is a flowchart which shows the subroutine program of a schedule input process. It is a flowchart which shows the subroutine program of a link production | generation process. (A) is a figure which shows the link verification 1 and (b) is a figure which shows the link verification 2 It is a flowchart which shows the subroutine program of other rules schedule input processing. It is a flowchart which shows the subroutine program of a data acquisition process (client side) and a data acquisition corresponding | compatible process (server side). It is a flowchart which shows the subroutine program of a server data display process (client side) and a server data display corresponding | compatible process (server side). It is a flowchart which shows the subroutine program of the designation | designated process of taking in selection data. (A) is a flowchart which shows the subroutine program of a data display process, (b) is a flowchart which shows the subroutine program of a work display process (task list). (A) is a flowchart which shows the subroutine program of the display process of a selection item, (b) is a flowchart which shows the subroutine program of a schedule display process (range selection display according to calendar date). (A) is a flowchart which shows the subroutine program of a work schedule simultaneous display process (display of the calendar and the task list of the range linked to the display range), (b) is a flowchart which shows the subroutine program of the overhead view display process (tree). It is. It is a transition diagram of a normal screen. It is a transition diagram of a bird's-eye view display (tree) screen. (A) is a figure which shows a bird's-eye view display (tree) screen, (b) is a figure which shows a bird's-eye view display (icon) screen. (A) is a figure which shows a bird's-eye view display (list) screen, (b) is a figure which shows a bird's-eye view display (column) screen. (A) is a figure which shows a plan new edit display screen, (b) is a figure which shows a plan existing edit display screen. (A) is a figure which shows a work new edit display screen, (b) is a figure which shows a work existing edit display screen. (A) is a figure which shows a plan new display screen, (b) is a figure which shows a plan new edit display (automatic work production | generation) screen. (A) is a figure which shows a plan existing display screen, (b) is a figure which shows a different-schedule new edit display screen. (A) is a figure which shows a different schedule schedule new edit display (work automatic generation) screen, (b) is a figure which shows a different schedule existing edit display screen. (A) is a figure which shows a normal screen display internal transition, (b) is a figure which shows a work list display screen. It is a figure which shows a work list display screen transition. It is a figure which shows a work (work list) plan (calendar) simultaneous display screen. (A) is a figure which shows the transition from a calendar display screen to another display screen, (b) is a figure which shows the internal transition of a calendar display. It is a figure which shows a plan (calendar) 1 month display screen. It is a figure which shows a plan (calendar) 2 week display screen. (A) is a figure which shows a schedule (calendar) 1 week display screen, (b) is a figure which shows a schedule (calendar) 1 day display screen. (A) is a flowchart showing a main routine program of a client terminal and a management server in a modified example, and (b) is a flowchart showing a subroutine program of data editing processing and data editing corresponding processing in the modified example. It is a flowchart which shows the subroutine program of the server synchronization process (client side) and server synchronization corresponding | compatible process (cloud server side) in a modification.

  Next, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing an overall configuration of a computer system according to the present invention. This computer system performs management of schedules (such as appointments) and management of jobs (jobs) in cooperation. A plurality of client terminals 2... Are connected to an in-house LAN (Local Area Network) 1 of company B, and are connected to the Internet 3 via the in-house LAN 1. A management server 4 composed of a cloud server is connected to the Internet 3. Further, a client terminal 2 composed of a mobile terminal taken out by an employee of company B or the like is also connected to the management server 4 via the Internet 3. The plurality of client terminals 2... Operate not as a stand-alone but as a client / server model. In addition, the case where it operates by stand-alone is mentioned later as a modification. The client terminal 2 is operated by employees (also referred to as users) belonging to each department such as a sales department, an accounting department, and a development department within the company. In the database 5 of the management server 4, the ID (identification) of each employee, the department name to which the employee belongs, the name of the employee, and the management of the plan (project), work, schedule, and other schedule (described later) Are stored in association with each other. This management data includes public management data consisting of schedules and tasks shared by each employee on the server, and private management data consisting of schedules and tasks managed individually by each employee. It consists of data. The private management data may be stored in the local client terminal 2 or the like without being stored in the database 5 of the management server 4.

  For example, in the case of an employee with ID 2803, the department to which the employee belongs is the development department and the name is Jiro, and data as shown in FIG. 1 is stored as management data. Note that the database 5 is specifically provided with an application server that controls the database, and the application server is configured to control and extract various data in the database. .

  The management data shown in FIG. 1 is classified into a multi-layered structure according to related matters from a high-level performance-related item to be performed to one or more low-level performance-related items to be performed in relation to the high-level performance-related item. This is input by operating Jiro's own client terminal 2.

  For example, when a specific technology development work is taken into consideration, the planning stage relating to the plan including the basic research plan 7 and the applied research plan 8 and one or more work necessary for concretely executing the plan. And one or more schedules necessary for concretely performing the task and a schedule stage related to other schedules (described later).

  Therefore, the management data is related to this plan by disassembling everything related to this technology development work step by step and expressing the contents and matters of the plan to be executed at the highest planning stage. A job item that represents the content or matters of one or more tasks that should be performed at the work stage and a plan that represents the content or matters of one or more tasks that should be performed at the scheduled stage in relation to the job It is classified into items, and each item is managed as a related item unit in association with the execution time. Furthermore, the management server 4 can also manage other rules that will be described in detail later.

  The plan items represent the contents and matters of the business plan for new technology development. This plan item has three hierarchies: a middle plan item immediately below the highest level ROOT plan and one or more subordinate plan items related to the middle plan item.

  The intermediate plan items include a basic research plan item expressing the contents and matters of the basic research plan 7 and an applied research plan item expressing the contents and matters of the applied research plan 8 related to the basic plan.

  The sub-planned items are related to the execution of the basic research plan 7 and include the experimental plan items and thesis preparation plan items that represent the contents and matters of the experimental plan 9 and thesis preparation plan 10 necessary or incidental to the execution. In addition, in relation to the execution of the applied research plan 8, there are a problem solution plan item and a patent acquisition plan item indicating the contents and matters of the problem solution plan 11 and the patent acquisition plan 12 necessary or incidental to the execution. .

  The work items represent the contents and matters of specific work necessary or incidental to the execution of each plan of the experiment plan 9, the paper preparation plan 10, the problem solution plan 11, and the patent acquisition plan 12. The work items include photography items and graph creation items related to the experiment plan 9, related paper collection items and experiment data arrangement items related to the 10th paper preparation plan, and problem collection items related to the problem solution plan 11. In addition, there are a matter for taking a photograph, a matter for patent search and a matter for producing a description related to the patent acquisition plan 12.

  Photographing items and graphing items represent the contents and matters of each work of photography 13 and graphing 14 necessary or incidental to the execution of the experiment plan 9 and related papers. The collected items and the experimental data arrangement items represent the contents and matters of each work of the related paper collection 15 and the experimental data arrangement 16 necessary or associated with the execution of the thesis preparation plan 10.

  The issue collection item and the photography item represent the contents and matters of each task of the issue collection 19 and the photography 21 necessary or incidental to the execution in connection with the execution of the issue solution plan 11 The search items and the description preparation items represent the contents and matters of each work of the patent search 22 and the specification preparation 24 necessary or associated with the execution of the patent acquisition plan 12 in connection with the execution of the patent acquisition plan 12.

  Scheduled items are related to each work of collecting related papers 15, patent search 22, and specification 24, and indicate the contents and matters of schedules necessary or related to the execution. 2nd meeting schedule item, 4th meeting schedule item regarding meeting with patent investigator, 5th meeting schedule item regarding meeting with patent attorney, etc.

  In FIG. 1, the first meeting schedule item related to the graph creation software meeting is a different schedule that the user has noted and stored in order to refer to the schedules of other users related to the graph creation 14. The three meeting schedule items are other schedules that the user has noted and stored in order to refer to other users' schedules related to the task collection 19. This will be described later.

  The first meeting schedule item relates to the work of the graph preparation 14 and represents the contents and matters of the first meeting schedule 17 related to the graph generation software meeting necessary or related to the execution, and the second meeting schedule item is related. In relation to the work of the paper collection 15, the contents and matters of the second meeting schedule 18 relating to the meeting with the paper researcher necessary or related to the execution are indicated. The scheduled items for the third meeting are related to the work of the task collection 19 and represent the contents and matters of the scheduled third meeting 20 related to the resolution of the researcher's tasks necessary or related to the tasks. Represents the contents and matters of the fourth meeting schedule 23 related to the meeting with the patent searcher necessary or related to the patent search work, and the fifth meeting schedule item is the work of preparing the description. The contents and matters of the fifth meeting schedule 25 related to the meeting with the patent attorney necessary or related to the performance are indicated.

  The aforementioned plan is a scheme designed to achieve a certain purpose. The highest plan is the ROOT plan 6, which is statically (automatically) stored in the client terminal 2 when the software of this system is installed. Therefore, this ROOT plan 6 does not need to be manually input by an employee (user).

  These plans have an execution time (specifically, an execution period) that determines when the plan will be achieved. As described above, the “execution period” of the plan is a period allowed for an employee (user) to achieve the plan. In this embodiment, the “execution period” is expressed as a “grace period”. To do. In the case of the ROOT plan 6, the grace period is infinite. Each of the basic research plan 7 and the applied research plan 8 has a finite grace period. The experimental plan 9 and the paper preparation plan 10 are specific plans for achieving the basic research plan 7 which is a higher-level plan. Therefore, the grace period of these specific plans is set within the range of the grace period of the basic research plan 7, which is a directly superordinate plan. Similarly, the grace period of the problem solving plan 11 and the patent acquisition plan 12 is also set within the range of the grace period of the applied research plan 8, which is a directly superordinate plan.

  Next, the work is a specific work necessary for specifically executing the plan. The tasks for achieving the experiment plan 9 include photography 13 and graph creation 14, and the execution time (specifically, the execution period) of these tasks is the range of the grace period of the experiment plan 9, which is a direct report. Inside. The work execution period is a period in which it is determined from when to when the work will be accomplished. As described above, the “execution period” of work is a period allowed for an employee (user) to accomplish the work, and in the present embodiment, this “execution period” is expressed as “grace period”. . The tasks for achieving the paper preparation plan 10 are collection of related papers 15 and arrangement of experimental data 16. These work grace periods are also within the grace period of the thesis preparation plan 10, which is a direct report. Tasks for achieving the task solution plan 11 include task collection 19 and photography (link) 21. These work grace periods are also within the grace period of the problem solving plan 11 which is a direct report. Furthermore, the grace period of work for the patent search 22 and the specification preparation 24 is also within the grace period of the patent acquisition plan 12, which is a direct report. Here, the “link” is information indicating the location of work (substance or actual data) that has already been generated, and is generated at a location different from the plan directly belonging to the entity.

  The photography 21 belonging to the problem solving plan 11 is a link to the photography 13 belonging to the experiment plan 9. Although not shown in FIG. 1, not only work links but also plan links may be introduced. By introducing such a link, a specific plan or work can belong to a plurality of plans at the same time.

  Next, a schedule is a performance-related matter for which a restraint period such as an appointment to be performed in a direct job is defined. This restraint period is set within the grace period of direct work. In the case of the management data shown in FIG. 1, there is a second meeting schedule 18 of a paper meeting with a researcher as a work schedule of the related paper collection 15, and a meeting with a patent researcher as a schedule belonging to the work of the patent search 22. There is a fourth meeting schedule 23 of the meeting, and as a schedule belonging to the work of the specification creation 24, there is a fifth meeting schedule 25 of a meeting with the patent attorney. In FIG. 1, the first meeting schedule item related to the graph creation software meeting is a non-temporal schedule recorded and recorded by the user in order to schedule other users in relation to the graph creation 14. The three meeting schedule items are other schedules that the user notes and stores in order to schedule other users in connection with the task collection 19. This other schedule will be described below.

  In FIG. 1, the third meeting schedule 20 of the assignment meeting is indicated by a broken line. The third meeting schedule 20 of this task meeting is a record of other employees' schedules as reference information. When making this schedule, there is a case where the schedule generated by other employees is referred to and recorded in the management data as other data.

  For example, if Taro from the sales department collects knowledge about new product issues and problems heard from customers and plans to solve them are recorded, the third meeting schedule 20 of the task meeting is applied research. This is a useful job and schedule for Jiro in solving the problems in Japan. As another example, suppose that Taro of the sales department plans to attend a product planning briefing event in a certain field. In the product plan briefing session, data is stored in the form of a time table in which a plan presentation is given from 10:00 to 12:00 and a specific product is explained from 13:00 to 14:00. Jiro may be particularly interested in “plan presentation” in this timetable. In such a case, Jiro can read and record the management data for other employees (for example, Taro) and record it in order to refer to the schedule.

  Further, the “first meeting schedule item regarding the graph creation software meeting” indicated by a broken line in FIG. The user notes and stores it in order to refer to other users' schedules related to the work of “graph creation”. This “first meeting schedule item relating to the graph creation software meeting” is, for example, as shown in a calendar display area of FIG. The title of the other schedule such as “scheduled meeting” is displayed, and 13: 00 to 15:00 is displayed as the period of the scheduled meeting. The user can participate in this other schedule and generate and register his own schedule item which is a schedule item of his / her performance related to the schedule item of the other user. In the example shown in FIG. 26, the participation period is announced only for the period from 13:00 to 14:00, and the restraint period from 13:00 to 14:00, among the scheduled meetings from 13:00 to 15:00 scheduled for other rules. Own schedule is created and registered. This schedule is not shown in FIG.

  In the management data described above, a plan (project) has a grace period, manages a plan or job (job) to which the plan belongs, and a link thereof, and serves as a search path indicating the position thereof. Here, the “path” is a character string that specifies the location of data in the computer. For example, the path of the patent acquisition plan 12 is “C: / ROOT plan / applied research plan”. As in this example, the path indicates the route of the upper plan from the ROOT plan 6 to the plan, and the terminal plan becomes the parent plan directly belonging to the plan. All plans other than the ROOT plan (top-level project) 6 and their links belong hierarchically under any plan and are constrained by the grace period of the upper plan. In addition, the name of the formal “plan” is represented by the full path name from the ROOT plan 6, and even if the “plan” of the same name is not linked, it is recognized as a completely different “plan”.

  A job and its links belong to one of the plans as well as the plan and have a grace period like the plan. A work has an arbitrary number of appointments and other schedules as its division units.

  The schedule has a period similar to the work, but the schedule is based on the assumption that the user (employee) 's action time limit is memorized, so that the period is a restraint period divided within the grace period of the work to which it belongs It is. Therefore, “schedule” is like a “work” record managed with the constraint period as a key.

  As described above, for example, as shown in FIG. 1, the management data belongs to a higher level plan branched from the highest level ROOT plan 6, a lower level plan branched from the higher level plan, and a lower level plan. It exists in memory in a tree structure (tree structure) such as a job and a schedule belonging to the job.

  Next, functions of the computer system in the present embodiment will be described with reference to FIG. A database 5 as an example of a storage means and an input means 70 for inputting performance-related items related to items to be performed by the user and a grace period that is the execution time to the database 5 are provided. When the user inputs the plan item A as an example of performance-related items and its grace period by the input means 70, the plan input process (see S7 in FIG. 3C) is executed, and the plan item A and its items are stored in the database 5. The grace period is memorized. At this time, the path (ROOT plan / plan A /) of the plan item A is generated by the cooperation management means 71 and stored in the database 5 (see S25 in FIG. 4A). The direct plan of the plan item A is a ROOT plan, and a path following the ROOT plan, that is, “ROOT plan / plan A /” is generated and stored in the database 5.

  Next, when the work item B directly under the plan item A and its grace period are input by the input means 70 (see S8 in FIG. 3C), the grace period of the work B is the grace period of the plan item A The judging means 72 judges whether or not they are consistent with each other. Specifically, it is determined whether or not the grace period of the work item B is within the grace period of the plan item A (see S31 in FIG. 4B). As shown in FIG. 2, when the grace period of the work B protrudes from the grace period of the plan item A (NO in S31), the work item B is not stored in the database 5 by the processing unit 73. . The x mark attached to “work item B” in FIG. 2 means that it is not stored in the database 5.

  When the work item C and its grace period are input by the input means 70 (see S8 in FIG. 3C), whether or not the grace period of the work item C is consistent with the grace period of the immediate plan item A Is determined by the determination means 72. Specifically, it is determined whether or not the grace period of the work item C is within the grace period of the plan item A (see S31 in FIG. 4B). If it is within the range (YES in S31), the work item C and its grace period are stored in the database 5 by the processing means 73. At that time, a path of the work item C (ROOT plan / plan A / work C /) is generated by the cooperation management means 71 and stored in the database 5 (see S35 in FIG. 4B). The superordinate plan directly belonging to the work item C is the plan item A, and a path following the plan item A, that is, “ROOT plan / plan A / work C /” is generated and stored in the database 5.

  Next, when the schedule item D and its restraint period are input from the input means (see S9 in FIG. 3C), the schedule period of the schedule item D is the grace period of the direct work item C as described above. The judging means 72 judges whether or not they are consistent. Specifically, it is determined whether or not the restraint period of the schedule item D is within the grace period of the work item C (see S46 in FIG. 5). If it is within the range (YES in S46), the scheduled item D and its grace period are stored in the database 5 by the processing means 73 (see S50 in FIG. 5). At that time, the same path (ROOT plan / plan A / work C /) as the direct work item C is determined by the cooperation management means 71 as the path of the scheduled item D.

  Next, when the schedule item E and its restraint period are input from the input means (see S9 in FIG. 3C), the schedule period of the schedule item E is the grace period of the immediate work item C as described above. The judging means 72 judges whether or not they are consistent. Specifically, it is determined whether or not the restraint period of the scheduled item E is within the grace period of the work item C (see S46 in FIG. 5). If it is within the range (YES in S46), the scheduled item E and its grace period are stored in the database 5 by the processing means 73 (see S50 in FIG. 5). At that time, the linkage management means 71 determines the same path (ROOT plan / plan A / work C /) as the directly related work item C as the path of the scheduled item E.

  As described above, the cooperation management unit 71 associates the multi-layer related items (for example, the work item C and its directly related plan item A) using the path that is a character string for specifying the location of the data in the computer. To be stored in the database 5. As a result, the multi-tier related items are managed in a unified manner. As a result, for example, it is possible to simultaneously display a schedule and its direct work. For example, in the schedule (calendar) 1-week display (see FIG. 30A) described later), the all-day schedule of “graph creation” is displayed, which should be displayed as a task list (task list). In FIG. 30 (a), since only the calendar is displayed, “graph creation” which is scheduled for the whole day is displayed in the calendar. However, when the task list and the calendar display are displayed simultaneously as shown in FIG. 26, the “graph creation” is displayed in the task list without displaying the calendar. Such control is possible because the schedule and other schedule and work are linked and managed in a unified manner, and is an advantage of the unified management.

  Further, for example, as shown in the relation display means in FIG. 2 (see S162 in FIG. 12A), a job C that has not yet been scheduled is displayed in the job list. If a schedule is entered, control is performed so that the task C disappears from the task list and is displayed on the calendar. Such control is possible because the schedule and other schedule and work are linked and managed in a unified manner, and is an advantage of the unified management.

  Next, hardware circuits of the client terminals 2... And the management server 4 will be described with reference to FIG. A CPU (Central Processing Unit) 30 as a control center, a ROM (Read Only Memory) 32 storing a control program and control data, a RAM (Random Access Memory) 31 functioning as a work area of the CPU 30, and a data rewritable An EEPROM (Electrically Erasable Programmable Read-Only Memory) 33 to be stored is connected by a bus 34. The bus 34 is connected to various devices via the interface unit 35. Examples of various devices include a communication unit 36, a display unit 37, an input operation unit 38, and the like. The communication unit 36 allows the client terminal 2 to communicate with the management server 4 via the in-house LAN 1.

  Next, a flowchart of a main routine program executed in the client terminal 2 and the management server 4 will be described based on FIG. The program for the client terminal 2 and the program for the management server 4 are downloaded and installed, for example, from a website that collects and distributes application software from a third party. The CPU 30 of the client terminal 2 executes a server data display process in step (hereinafter simply referred to as S) 1 and executes a data editing process in S2.

  This server data display process (S1) is a process for the user (employee) to display the edited management data on the client terminal 2. The data editing process (S2) is a process for newly inputting or updating the management data shown in FIG. Data or a command is selected in the server data display process (S1), and the selected command is executed on the selected data in the data editing process (S2). When the server data display process (S1) is performed in the client terminal 2, a server data display corresponding process, which is a control corresponding to the server data display process (S1), is executed in the management server 4 (S3). Further, when the data editing process (S2) is performed in the client terminal 2, the management data corresponding to the database 5 of the management server 4 needs to be updated to a new one. For this purpose, the CPU 30 of the management server 4 executes a data editing corresponding process in S4.

  Next, a flowchart of a subroutine program of the data editing process in S2 and the data editing corresponding process in S4 will be described with reference to FIG. In the data editing process, six program modules S7 to S12 are selected and executed in parallel. For example, control is performed so that six program modules are sequentially selected and executed one by one, such as S7 → S8 → S9 → S10 → S11 → S12 → S7.

  The plan input process in S7 is a process in which the user (employee) operates the input operation unit 38 of the client terminal 2 to input “plan” in the management data. The work input process of S8 is a process of inputting “work” in the management data. The schedule input process of S9 is a process of inputting “schedule” in the management data. In addition, as will be described in detail later, a process of generating its own schedule (autonomous schedule) from another schedule is also included. The link generation process of S10 is a process of generating a link to the already input actual data in the work or plan, like the above-described photography (link) 21. The other-schedule schedule input process of S11 is a process for newly creating another schedule and editing the authority of the existing schedule.

  The data fetching process of S12 is a process for fetching and recording the other person's “schedule” in the management data as reference information. Corresponding to this data capture process (S12), the management server 4 executes a data capture process (S17). The data fetch handling process in S17 is a process for transmitting the management data disclosed (shared) by the employee to be fetched to the client terminal 2 of the desired employee.

  Next, a flowchart of the subroutine program for the plan input process shown in S7 will be described with reference to FIG. This plan input process is a process in which the user inputs his / her plan according to the edit display screens of FIGS. First, it is determined in S20 whether or not there has been a plan input operation. If the employee operates the input operation unit 38 of the client terminal 2 and performs a plan input operation, a determination of YES is made in S20 and control proceeds to S21. In the plan input operation of S20, specifically, an input designation of a direct plan that designates which higher level plan the input plan belongs to and a grace period of the input plan are input.

  For example, the direct plan “ROOT plan” is designated on the overhead view (tree) display screen of FIG. 14B, and the applied plan name is “applied research plan”, and the grace period is “February 1, 2016”, for example. Enter "Sun-December 1, 2016". The “ROOT plan” does not need to be generated because it exists statically. There is always one top-level special plan with an infinite grace period for each activated application, and all items are uniquely recognized by a path starting from here. Actually, in the case of a server, there is a “ROOT plan” for each management user, and each management user assigns a “virtual ROOT plan” for each user directly under the “ROOT plan” of each management unit.

  Next, the control proceeds to S21, and it is determined whether or not the input grace period is within the grace period of the direct plan (for example, applied research plan). If the input grace period is outside the grace period of the direct plan, the control proceeds to S22, an error is displayed on the display unit 37 of the client terminal 2, and then the control proceeds to S20. This error display is accompanied by a message display such as “Please input again because the grace period of the input plan is outside the range of the grace period of the immediate plan”.

  If the user who has seen this error display re-enters the correct grace period, S20 is determined as YES, and control proceeds to S21 again. If it is determined in S21 that the grace period is within the grace period of the direct plan, the control proceeds to S23, and it is determined whether or not the existing plan is not edited but a new generation. For example, as shown in FIG. 16, when a new plan edit is executed from the tree display, a new plan edit display screen shown in FIG. 19A, which will be described later, is displayed on the display unit 37 of the user's client terminal 2, and will be described later. Thus, the plan name, the grace period of the plan, and the like are input and the contents are stored in the database 5.

  And it determines with YES by S23 and control progresses to S24, and takes over the authority (access right etc.) of a creator about the newly produced | generated plan. Each user who is an employee is preset with authority to access various data and editing authority. In S24, control is performed to take over the authority set for the user for the newly generated plan. Next, the control advances to S25, and a control is performed in which a path following a direct plan (for example, a ROOT plan) is determined and the plan is stored in the database 5 together with a grace period. All plans are not disclosed when newly created.

  On the other hand, for example, when the planned existing edit is executed from the tree display shown in FIG. 16, it is determined NO in S23, and the planned existing edit display screen shown in FIG. An outline, a grace period, etc. of an existing plan (patent acquisition plan in the example of FIG. 19B) specified as will be described later based on this plan existing edit display screen are edited by the user and stored in the database 5. The Then, in S26, it is determined whether or not the authority of the existing plan is to be edited. In the case of editing, the control proceeds to S27, and a process for editing the authority of the existing plan is performed. If necessary, control is performed to set a right (access right, etc.) for a specific individual or group and disclose the plan. Following the processing of S27, control proceeds to S25. Even if the authority of the existing plan is not edited, the control proceeds to S25, and a process for storing the outline of the plan edited by the user, a grace period, and the like is performed.

  Next, the flowchart of the subroutine program for the work input process shown in S8 will be described with reference to FIG. This work input process is a process in which a user inputs his / her work in accordance with an edit display screen shown in FIGS. First, it is determined whether or not a work input operation has been performed in S30. If the user operates the input operation unit 38 of the client terminal 2 to perform a work input operation, a determination of YES is made in S30 and control proceeds to S31. In the work input operation in S30, for example, the user performs an operation of creating a new work after designating a direct plan "patent acquisition plan" on the overhead display (tree) display screen of FIG. As a result, the new task edit display screen of FIG. 20A is displayed on the display unit 37, and the task name and its grace period are input.

  If there is such an input operation, it is determined in S31 whether or not the input grace period is within the range of the grace period of the direct plan. If it is beyond the grace period of the direct plan, the control proceeds to S32, an error is displayed on the display unit 37 of the client terminal 2, and the control proceeds to S30. This error display is accompanied by a message display such as “Please input again because the grace period of the input work is out of the grace period of the immediate plan”.

  The direct plans to which the work belongs are only actual plans and do not include plan links. Therefore, when a plan link is selected and specified, an error is displayed in S32. If the input grace period is within the range of the grace period of the direct plan, the control proceeds to S33, and it is determined whether or not it is a new generation rather than an editing of an existing job. For example, as shown in FIG. 16, when new job editing is executed from the tree display, it is determined as YES by S33 and the control proceeds to S34, and the authority (access right, etc.) of the creator is taken over.

  Next, the control advances to S35, and a process of determining a path following the direct plan and storing the work in the database 5 together with a grace period is performed. For example, the work path of the specification creation 24 is “C: / ROOT plan / applied research plan / patent acquisition plan / specification creation”. In this way, by storing the plan and the work related to the plan in association with each other, it is possible to manage the plan and the work in a unified manner, and not only the management of the work and the schedule but also the plan for the purpose of performing the work. A series of business management from the upper level to the lower level is possible, including those of the higher level concept. Here, “centralized management” means that management is performed collectively using the same means and tools. All work is private at the time of new creation.

  On the other hand, for example, when task existing editing is executed from the tree display shown in FIG. 16, it is determined NO in S33, the task existing editing screen shown in FIG. 20B is displayed on the display unit 37, and the user edits The summary of work entered as, and the grace period are edited.

  When the user edits the authority of the existing job, the determination is YES in S36, and the control proceeds to S37, where processing for editing the authority of the existing job is performed. Then, if necessary, control is performed to set a right (access right or the like) for a specific individual or group and disclose the work. Following the process of S37, control proceeds to S55. Even if the authority of the existing job is not edited, the control proceeds to S35, and a process of storing an outline of the job edited by the user, a grace period, and the like is performed.

  Next, the flowchart of the subroutine program for the schedule input process shown in S9 will be described with reference to FIG. This schedule input process is a process in which a user inputs his / her schedule according to an edit display screen shown in FIGS. 21 (a) to 22 (a) described later. First, in S40, it is determined whether or not a scheduled input operation has been performed. The user operates the input operation unit 38 of the client terminal 2 to execute, for example, scheduled new editing, scheduled new editing (automatic job generation), scheduled existing editing, or other schedule existing editing from the tree display shown in FIG. In this case, it is determined as YES by S40, and the control advances to S41 to determine whether or not there is a direct job. If anything other than scheduled new editing (automatic job generation) is executed, the determination at S41 is YES and control proceeds to S42, and there is no overlap between the same type of schedule belonging to the immediate job and the constraint period. Is determined. If there are overlapping constraint periods, the control proceeds to S43 and an error is displayed on the display unit 37 of the client terminal 2, and then the control proceeds to S40. This error display is control for preventing the inconvenience that the person in charge cannot execute one of the overlapping schedules when the constraint periods of the schedules overlap. This error display is accompanied by a message display such as “Please input again because the input scheduled constraint period overlaps with another scheduled constraint period”. If there is no overlap, the control proceeds to S46.

  On the other hand, when the scheduled new editing (automatic job generation) is executed, the scheduled new editing display (automatic job generation) screen of FIG. 21B is displayed on the display unit 37, and the control proceeds to S44. . The new schedule edit (automatic task generation) is an edit for generating a schedule in a state where a direct task is not generated, and it is necessary to generate a direct task for the schedule before generating the schedule. Therefore, in S44, the name of the plan to be generated and the grace period of the direct plan are set as input contents, and the direct job of the job to be generated is generated. The process is performed in S45 (see FIG. 4B). In S45, the grace period of the input direct plan is copied as a grace period of work to be generated. Following S45, control proceeds to S46. In S46, it is determined whether or not the scheduled restraint period is within the range of the grace period of the direct job. If it is not within the range, the control proceeds to S43, an error is displayed on the display unit 37 of the client terminal 2, and then the control proceeds to S40. This error display is accompanied by a message display such as “Please input again because the entered constraint period is outside the grace period of the immediate work”.

  If it is within the grace period, control proceeds to S47, where it is determined whether the schedule is generated from another schedule. As described above, there are two types of schedules: autonomous schedules and other schedules. The other rule schedule is a schedule in which another person is involved, for example, having a meeting with another employee (user). For this reason, the “scheduled” restraint period cannot be arbitrarily set or changed. On the other hand, an autonomous schedule is a schedule in which no other person is involved, and the restraint period of “schedule” can be freely set and changed.

  If the above-described scheduled new editing, scheduled new editing (automatic task creation) or scheduled existing editing is being executed, it is determined NO in S47, and the control advances to S48. It is determined whether or not. If scheduled new editing or scheduled new editing (automatic job generation) is being executed, control proceeds to S49, and the creator's authority (access right, etc.) is taken over. Next, control proceeds to S50, where the schedule is registered in the schedule list of the work to which it belongs and stored in the database 5 together with the restraint period and the like. This storage process includes an autonomous schedule generated from another schedule (in the case of YES in S47). All schedules and other rules are not disclosed when newly created.

  On the other hand, if the above-mentioned scheduled existing editing is being executed, it is determined NO in S48, the scheduled existing editing display screen of FIG. 22A is displayed on the display unit 37, and the schedule designated by the user as the editing target. The outline, the restraint period, etc. are edited by the user. In the case of editing the restraint period, it is determined NO in S53 and returns once. When the control reaches S42 and S46 in the next loop of the main routine (see FIG. 3B), the determination in S42 and S46 is made. If it is determined NO, an error process in S43 is performed. Next, the control advances to S53, and a process for editing the authority of the existing schedule is performed. If necessary, a control is performed to set a right (access right, etc.) for a specific individual or group and to release the schedule. Following the processing of S54, control proceeds to S50.

  If the above-mentioned other-temporary schedule existing editing is executed and the participation expression button 58 shown in FIG. 23B is clicked, the control proceeds to S51. The click of the participation expression button 58 is an operation for the user to participate in the other schedule that is publicly shared in S108 described later. In S51, it is determined whether or not the constraint period scheduled to be generated is within the range of the constraint period scheduled to be generated. In the case of originally scheduled for other rules, no error is displayed (although a warning is displayed) even if the restraint period (holding period) is outside the range of the grace period of the direct work. Because other rules need only exist as references within the same job, other rules are not affected by the grace period of the job to which they belong.

  However, when participating in other schedules, the participant's own schedule (autonomous schedule) is generated and registered, and is not merely a reference item. As a result, the determination in S51 is necessary. If the constraint period scheduled to be generated extends beyond the constraint period other than the generation source, control proceeds to S43, an error is displayed on the display unit 37 of the client terminal 2, and control proceeds to S40. This error display is accompanied by a message display such as “Please input again because the constraint period scheduled to be generated is outside the range of the constraint period other than the generation source”.

  If YES is determined in S51, the control proceeds to S52 and corresponds to another schedule (for example, another schedule name: assignment collection 19: title: third meeting schedule 20 of the assignment meeting indicated by a broken line in FIG. 1). Generate and register an autonomous schedule. This “autonomous schedule” is referred to as “schedule generated due to other schedules”. Further, a process of registering and storing the user who has expressed the participation in the participant list in the other schedule of the generation source is performed. This participant list is stored in the database 5. If the user's participation time in the event is shorter than the actual event time, the new schedule button is displayed instead of the participation announcement button 58, and the new schedule editing screen (see FIG. 21A) is displayed, and the shortened restraint period is displayed. You can also announce participation by setting and generating. Further, the post-control of S52 proceeds to S48. When the other schedule is publicly shared by the management server 4, the participant list also serves as a schedule list generated based on the other schedule to which the schedule belongs.

  Next, a flowchart of the subroutine program for the link generation process shown in S10 will be described with reference to FIG. In S80, it is determined whether or not a link generation operation has been performed. If there is no link generation operation, the process returns. If the user performs a link generation operation using the input operation unit 38 of the client terminal 2, the control proceeds to S81. This link generation operation is an operation for specifying and inputting a link target (for example, photography) and a direct report (for example, a problem solving plan). This “photographing” of link target designation is to designate, for example, photography 13 belonging to the experiment plan 9 shown in FIG.

  In S81, it is determined whether or not the grace period is within the range of the direct report. In the above example, it is determined whether or not the grace period of the photography 13 as the designated link target is within the range of the grace period of the problem solution plan 11 which is a direct plan. If it is determined that it is not within the range, the control proceeds to S82, an error is displayed on the display unit 37 of the client terminal 2, and then the control proceeds to S80.

  If the grace period is within the range of the direct plan, the control advances to S83 to determine whether or not the actual link to be generated is work. Here, the “link entity” is the work or plan of the entity whose location is specified by the link. There are two types of “work” and “plan” that can be linked. In the case of “work”, a determination of YES is made in S83, and the control advances to S84 to determine a path following the direct plan and store the link in the database 5 together with a grace period. For example, the path of photography (link) 21 is “C: / ROOT plan / applied research plan / problem solving plan / photographing”.

  On the other hand, if the entity of the link to be generated is “plan”, the control advances to S85 to determine whether or not the link of the plan is to be generated below the entity. In the case of “plan”, as described with reference to FIG. 1, for example, a higher-level plan such as the basic research plan 7 and the applied research plan 8 and a lower-level plan such as the experiment plan 9 and the problem solving plan 11. There is a hierarchical structure. As a result, if the plan link is allowed to be generated below the entity, there is a contradiction that the same plan exists under the plan. In the example of FIG. 1, for example, a contradiction arises in that a link of the applied research plan 8 is generated below the applied research plan 8.

  Therefore, when a plan link is to be generated below the entity, a determination of YES is made in S85 and control is performed so that an error display in S82 is performed. This error display is accompanied by a message display such as “The link of the input plan is about to be generated below the entity. Please input again to generate it in the correct hierarchy”. If NO is determined in S85, the control proceeds to S86. On the other hand, in the case of work (in the case of YES in S83), since the link of the work cannot be generated below the entity of the link, the link generation destination plan is within the link grace period. All you need to do is check for it.

  Next, the outline of the processing of S86 to S92 will be described first. It is determined whether or not there is another link having a grace period equal to the grace period of the plan of the generation destination below the entity of the planned link to be generated (S86). It is determined whether or not the entity exists between the route plan and the generation destination plan (S89). If it exists, an error is displayed (S82).

  This will be described with reference to FIGS. 7 (a) and 7 (b). First, referring to FIG. 7 (a), the contents of FIG. 7 (a) are shown in parentheses in the outline description text as follows. “Determining whether there is another link having the same grace period as the grace period of the plan of the generation destination (plan X) below the entity (plan Y) of the plan link to be generated (link of plan Y) If it exists, it is determined whether or not the entity (plan X) of the existing link (link of plan X) exists between the route plan and the generation plan (plan X). Displays an error. "

  As shown in FIG. 7A, if the link of “Plan Y” is generated in the lower layer of “Plan X” and then the link of “Plan X” is allowed to be generated in the lower layer of “Plan Y”. It becomes a reference, and a contradiction arises that each link exists in the lower layer of each of X and Y. "Circular reference" means "plan X"-> "link of plan Y"-> "plan Y"-> "link of plan X"-> "plan X" when searching the lower level items from the route plan based on the path "Is a phenomenon that becomes an infinite circulation loop. In order to eliminate such a contradiction, if there is even one link below the actual state before link generation, monitor that there is no link entity between the route plan and the destination plan. -ing

  However, in fact, the fact that “link of plan X” is generated below “plan Y” must have the same or shorter grace period of “plan X” than the grace period of “plan Y”. On the contrary, if a “link of plan Y” is generated below “plan X”, the grace period of “plan Y” must be shorter than or equal to the grace period of “plan X”. Therefore, when the grace period of the generation plan (plan X) and the grace period of the link to be generated (link of the plan Y) are different, the check can be omitted.

  In the case of FIG. 7B as well, inconsistency of the circular reference occurs. When the contents of FIG. 7B are inserted in parentheses in the above description text, it is as follows. “Determining whether there is another link having the same grace period as the grace period of the plan of the generation destination (plan X) below the entity (plan Y) of the plan link to be generated (link of plan Y) If it exists, it is determined whether or not the entity (plan X) of the existing link (link of plan X) exists between the route plan and the plan of the generation destination (plan A1B2C1). Displays an error. "

  Returning to FIG. 6, the processing of S86 to S92 will be described in detail. By S86, it is determined whether another link having the same grace period as the grace period of the plan of the generation destination exists below the entity of the planned link to be generated. If there is no such control, the control proceeds to S84, but if there is even one, the control proceeds to S87. In S87, the number of existing links is defined as N. Next, in S88, I is set to “1”, and in S89, it is determined whether or not the entity of the I-th link exists between the route plan and the generation destination plan. If it exists, the control proceeds to S82 and an error is displayed on the display unit 37 of the client terminal 2. This error display is accompanied by a message such as “circular reference conflict occurs”.

  On the other hand, if NO is determined in S89, the control proceeds to S90, I is incremented by "1", and whether or not "I = N + 1" is determined in S91. If not yet I = N + 1, the control returns to S89. This loop of S89 → S90 → S91 → S89 is repeatedly executed, the determination of S89 is performed for all links (N links), and when all are determined to be NO, a determination of YES is made in S91 and control is performed. Proceed to S92. In S92, I and N are cleared and the value is set to zero. Thereafter, the control proceeds to S84, and a process of determining a path following the direct plan and storing the link in the database 5 together with a grace period is performed. In the case of work, since it is impossible to generate a link below it, it is sufficient to check that the link generation destination plan is longer than the link grace period.

  Next, the flowchart of the subroutine program of the other schedule input process shown in S11 will be described with reference to FIG. This other-scheduled schedule input process is a process in which the user edits the other-scheduled schedule in accordance with any one of the edit display screens shown in FIGS. First, in S99, it is determined whether or not an input operation scheduled for other rules has been performed. If not, this subroutine program returns. For example, when another rule schedule new edit (automatic job generation) is executed from the tree display shown in FIG. 16, the other rule schedule new edit or other rule schedule existing edit is executed from the tree display via the task existing edit display. If YES, the determination at S99 is YES and control proceeds to S100.

  In S100, it is determined whether or not a direct job exists. If a task other than new editing of other schedules (automatic task generation) has been executed, there is already a direct task, so control proceeds to S101, and the input constraint period of the other schedule is the grace period of the direct task It is determined whether it is within the range. Since other rules are events, the substance of the restraint period is the holding period. That is, there is no problem even if the grace period of the work to which the restraint period of the other schedule belongs belongs because of reference information such as a schedule and a time table.

  However, consistency is better if it falls within the grace period of the work to which the other schedule belongs. Therefore, when the grace period of the work to which the other-law scheduled restraint period belongs is exceeded, the control proceeds to S105, and a warning is displayed on the display unit 37 of the client terminal 2 to alert the user. . In addition, if the user determines whether or not to create another schedule beyond the work grace period, and the user inputs a generation instruction, S106 is determined as YES and control proceeds to S102. To control. If the user inputs an instruction not to generate, it is determined NO in S106 and the control returns to S99.

  In S102, it is determined whether or not it is a new generation rather than an existing other schedule editing. When the other schedule schedule new edit is executed and the other schedule schedule new edit display screen of FIG. 22B is displayed, the user generates a new schedule of another schedule according to the edit display screen, and at S102. It determines with YES and control progresses to S103. In S103, a process of taking over the authority (access right, etc.) of the creator for the generated other schedule is performed. Next, the process proceeds to S104, where the other rule schedule is registered in the other rule schedule list of the work to which it belongs and stored in the database 5 together with the constraint period. All other schedules are not disclosed to anyone other than the creator at the time of new creation.

  On the other hand, when the other-scheduled schedule existing edit is executed, it is determined as NO in S102, and the other-scheduled schedule existing edit display screen of FIG. Editing of titles and outlines is performed. When the user edits the authority of the existing other schedule (such as access right), the determination in S107 is YES and the control advances to S108, where the process for editing the authority of the existing other schedule is performed. Then, if necessary, control is performed to set the authority (access right, etc.) for a specific individual or group and disclose the other schedule. Following the processing of S108, control proceeds to S104. If the user wants to participate in this published other schedule, the other schedule existing edit is executed and the other schedule existing edit display screen (see FIG. 20) is displayed on the display unit 37 of the client terminal 2 to announce participation. Click the button 58. As a result, participation is possible by the control of S47 → S51 → S52 described above. Control proceeds to S104 after the processing of S108. Even when the authority of the existing schedule of other rules is not edited, the control advances to S104 to perform processing for storing an outline of the schedule of other schedules edited by the user, a grace period, and the like.

  Next, a flowchart of the subroutine program of the data fetch process shown in S12 will be described with reference to FIG. In this data fetching process, when it is desired to fetch from the management server 4 "the schedule of others generated normally regardless of other schedules", the schedules of these other persons are converted into their other schedules or schedules, It is taken in. At the time of conversion, it is possible to improve the convenience for the user if it is possible to identify who is referring to the schedule by embedding owner information or the like for specifying who is the schedule to be captured in other rules.

  First, in S115, it is determined whether or not there has been a browsing operation for browsing other person's management data. If the employee inputs his / her ID and performs an operation of transmitting a browsing request to the management server 4, the control proceeds to S116, and server data display processing is executed. Correspondingly, in the management server 4, a server data display corresponding process is executed in S117. These processes are processes for causing the client terminal 2 to display the public management data that is authorized to be browsed by the person who wants to browse the public management data composed of plans, tasks, and schedules stored in the database 5. There will be detailed later. Although the data itself extracted by the management server 4 in accordance with the browsing request is under server management, it is private management data specific to the client (user management state) when it is imported from the management server 4 to the client terminal 2. An employee (user) who saw the management data of another person displayed in accordance with the browsing request in S116 operates the input operation unit 38 of the client terminal 2 to select a capture range from the referenceable data (S118).

  Next, control proceeds to S119, where it is determined whether the selection range has been changed. If there is, the process returns to S118 to select the capture range again. If there is no change in the selection range, the control advances to S120, where it is determined whether or not to convert the normally generated schedule of the other person into its own schedule. In the case of conversion to the own schedule (autonomous schedule), the control proceeds to S124, and after the process of converting the normally generated schedule of the other person into the own schedule (autonomous schedule) is performed, the process proceeds to S122. On the other hand, when converting the normally generated schedule of the other person into another schedule, the control proceeds to S121, and after converting the normally generated schedule of the other person into its other schedule, the process proceeds to S122. In S122, a process for designating the destination of the selection data is performed. This process is a process of designating directly under which data the selected data to be acquired is to be acquired, that is, specifying the directly superordinate data to which the selected data belongs, which will be described in detail later.

  Next, the control advances to S123, and processing for taking the selected data into an item designated as locked (temporarily unchangeable) user management data is performed. When the item of the other person is taken into the own plan by the above-described S124, it is converted into own data at the time of taking in. For each item taken in, all the elements including the grace period are locked (temporarily unchangeable) at the time of taking in without basically distinguishing from each other. In other words, the items treated as other rules are only the other rules.

  In addition, other people's schedules that are normally generated regardless of other schedules are extracted, but the other person's schedule that was selected during the data acquisition process is usually reference information. The schedule is converted to “other schedule”, and when there is an instruction from the taker, the schedule of the other person can be converted to “your schedule”. By doing so, it is also possible to execute scheduling tones with others who are acting together in the same way as scheduled posting.

  In addition, when converting other company's items into their own data, other people's schedules generated due to other schedules will be excluded, and it will no longer be possible to see other people's schedules associated with the participant list. It is possible to identify who was referring to the schedule by allowing the owner information, etc. to be written to the participant list as text information such as names and annotations instead of references and pointers of other rules. It becomes possible. In addition, when using other schedules without sharing them, it is possible to write down only the main members who actually need to know who participates as their own notes. It becomes.

  The action of “capturing data” in the present embodiment refers to capturing data disclosed to a specific viewing authority outside the private management data into the private management data as its own management data. Since the private management data is mainly for personal use, it is usually managed and used by each local system. However, in the present situation where terminals are diversified as in recent years, the private management data is stored in the management server 4. In general, the cloud synchronization system is configured by synchronizing with the private management data stored locally in a plurality of terminals using the data in the management server 4 as a core.

  The term “synchronization” in the present embodiment refers to synchronization performed to maintain the consistency between the private management data. The “data fetching process” is used when fetching another person's public data items into his / her private management data, and the target data is different from that in the synchronous process. Although the extracted data itself is under server management, it becomes private management data specific to the client (user management state) when it is imported from the server to the client side.

  Other people's schedules that have been reserved and created for other public schedules (the schedule is generated based on other schedules) is an expression of participation in other schedules, but is different from other schedules. In addition, the type is the same type as the other person's schedule that is normally generated regardless of other schedules. “Normally generated other person's schedule” is only related to the job to which it belongs, but “other person's schedule generated due to other schedule” is also related to the other schedule.

  Therefore, in the present embodiment, “schedules normally generated from work” and “schedules generated due to other schedules” are considered separately. “Schedule of other person generated due to other schedule” and “My schedule generated from other schedule” and “My schedule normally generated from work” could be viewed simultaneously However, at the time of capture, “the schedule of the other person generated due to the schedule of other rules” is not converted into the schedule of other rules, but is made up of the ID and the binding time at the time of reservation in advance. By creating a “participant list” and giving it to other schedules, it is possible to check the members who participate in the same event and their event stay time without referring to “schedules of others generated from other schedules” It is configured as follows.

  The “other person's schedule generated as a result of another schedule” is excluded when the selected data is extracted. In order to obtain the latest information not only when the publicly announced other-schedule schedule is expressed (participation schedule is generated and registered in the participant list), but also when it is simply referenced Must log in to the management server 4. “Synchronization processing” is used when the same user wants to maintain the consistency of local data among a plurality of client terminals 2 in cloud synchronization. In this embodiment, the private management data in the database 5 is synchronized. It is a cloud server system that maintains data consistency between client terminals 2 as a center, and is internally independent of a program that operates public management data.

  In the “data fetching process”, the present embodiment shows fetching of the public part of the system that handles public management data. However, in the point of selecting and fetching all or part of the published data. Is the same in the case of peer-to-peer. The public management data itself in the shared server itself can be rewritten directly within the authority at the time of login, except for backup operations, etc., but is not rewritten by synchronization processing or the like.

  It is not necessary to display the other person's schedule generated based on the other schedule (the other person's independent schedule converted from the other schedule in the case of YES in S51). Even if necessary, it is complicated and meaningless to display in comparison with the normal schedule, and it is considered that the schedules are usually due to the same schedule of other rules. It is enough to display the “Participant List” alone. In the case of a shared work in a group that is executed only for a plurality of members belonging to a certain group, each member belonging to the group can generate a schedule belonging to the shared work. In that case, everything other than the schedule generated by itself is taken in as a schedule of other rules. It is also possible to generate its own schedule (participate in other schedule of temperament) due to this schedule of other rules (see S52).

  Next, a flowchart of the subroutine program of the server data display process and the server data display corresponding process shown in S116 and S117 will be described with reference to FIG. In the case of this processing, the client side actually receives the service of the management server 4 within the authority after logging in to the management server 4. When an employee operates his / her client terminal 2 and selects a display range from management data (for example, public management data) that can be referred to from among the management data stored in the database 5 and performs a browsing operation. The browsing request (including its own ID) is transmitted to the management server 4 (S150). The management server 4 receives it (S151).

  The database 5 stores the access authority in advance associated with each user ID, and the management server 4 searches the access authority based on the received ID, and the employee who has issued the browsing request has the browsing authority. It is determined whether or not it has. When there is no access authority, an error display etc. is performed and the browsing is prohibited. In addition, when a user accesses a sharing plan or shared work that is executed only for a plurality of members belonging to a certain group, access from persons other than the members of the group is prohibited. The management server 4 also performs access authority control.

  Next, the management server 4 performs a process of extracting all data for which the employee has the viewing authority in accordance with the “browsing request” (S152). Next, in S153, the extracted data excluding the schedule of the other person generated due to the other schedule is returned to the client terminal 2 as the extracted data. The client terminal 2 receives it (S154), and displays it on the display unit 37 in S155.

  If the work extracted in S152 includes another schedule, it is displayed as the other schedule as it is, but as described above, another person's schedule generated based on the other schedule (YES in S51). In other cases, the independent plan of others converted from other schedules is not displayed. Since the person who expresses the participation in the other schedule can be confirmed in the “participant list” held by the other schedule, it is usually unnecessary to browse the schedule of the other person generated based on the other schedule. For this reason, the data excluding the schedule of the other person generated due to the other schedule is returned to the client terminal 2 as extracted data (S153). In addition, other people's schedules that are normally generated regardless of other schedules are extracted, but the other person's schedule that was selected during the data acquisition process is usually reference information. If you convert it to “other-schedule” and control it so that it can be converted to “your own schedule” when there is an instruction from the acquirer, There is an advantage that scheduling tones can be executed by scheduled posting.

  Next, the subroutine program of the designation process for fetching the selection data shown in S122 will be described based on the flowchart shown in FIG. There are three types of data to be acquired selected based on FIG. 9, in the case of only a schedule and other rhythm schedule, in the case of a schedule and other rhythm schedule and work, and in the case of a schedule and other rhythm schedule and work and plan. If the selected data is either a schedule, a different schedule, a work, or a schedule, a different schedule, a work, and a plan, it is determined NO in S130, and the control advances to S131 for selection. Limit data capture to plans only.

  In this state, when the user designates the plan of the import destination, it is determined whether or not the grace period of the selection item is within the grace period of the designated plan (S132). When the determination result in S132 is YES, processing for designating the plan designated in S133 as the import destination is performed. On the other hand, if the determination result in S132 is NO, an error is displayed on the display unit 37 of the client terminal 2 in S134. This error display is accompanied by a message display such as “Please enter again because the grace period of the selected item is out of the range of the grace period of the designated plan”.

  On the other hand, if the selected data is only a schedule and another schedule, the determination is YES in S130 and the control advances to S135 so that not only the plan but also the work can be designated as the destination of the selected data. In this state, if the user designates a plan as the import destination, S136 determines YES and the control proceeds to S144. In S144, it is determined whether or not the own restraint period is within the designated grace period. If the determination result is YES, the control proceeds to S137. On the other hand, if the determination result in S144 is NO, the control proceeds to S143, and an error is displayed on the display unit 37 of the client terminal 2. This error display is accompanied by a message display such as “Please input again because the constraint period of the selected schedule is out of the range of the specified plan grace period”.

  If "plan" is specified as the import destination item even though the selected data is "schedule", there is no data for "task" as a direct item of "schedule and other rules" It will be. Therefore, a process of generating “work” is performed in S137 and S138. First, in S137, the name of the plan to be taken in and the grace period of the designated plan are set as input contents, and a process of creating a direct job is performed. Next, a work input process is performed in S138. The specific contents of this work input process are shown in FIG. The grace period of the specified plan is copied as the grace period of the generated work. In step S139, the generated work is designated as the import destination.

  On the other hand, when the user designates a job as the import destination, the determination is YES in S140 and the control advances to S141, and it is determined whether or not the scheduled restraint period of the user is within the designated work grace period. If the determination result is YES, a process of designating the designated work as the import destination is performed in S142. On the other hand, if the determination result in S141 is NO, the control proceeds to S143, and an error is displayed on the display unit 37 of the client terminal 2. This error display is accompanied by a message display such as “Please re-enter because the selected scheduled restraint period is outside the specified work grace period”.

  In addition, when there are multiple names of the selected schedule, the user decides whether to create all of the multiple schedules as higher-level work, or to use the name of the first selected schedule as a candidate and use or edit it. It is better to leave it to. If “schedule” is designated when the selected data is only a schedule, NO is determined in S140 and error processing is performed in S143. This is an error display because an operation to generate a “plan” is performed subordinate to the “schedule”.

  Next, a flowchart of the subroutine program for the data display process shown in S1 will be described with reference to FIG. In this data display process, the display screen is actually a user interface for editing operation. In this data display process, four program modules S160 to S163 are selected and executed in parallel. For example, control is performed so that four program modules are sequentially selected and executed one by one, such as S160 → S161 → S162 → S163 → S160.

  The task display process (task list) executed in S160 is for the employee (user) to display his / her multiple tasks on the display unit 37 (see, for example, FIG. 24B). The schedule display process (displacement selection display by calendar year / month / day) executed in S161 is a process for selecting a scheduled calendar of one month, two weeks, one week or one day and displaying the work belonging to the range. (See, for example, FIGS. 28 to 27). The work schedule simultaneous display process (display of a calendar and a task list in a range linked to the display range) executed in S162 displays the work list and the scheduler calendar simultaneously (see FIG. 26). The bird's-eye view display process executed in S163 displays the tree-shaped management data shown in FIG. 1 as a tree as it is.

  Next, the flowchart of the subroutine program of the task display process (task list) shown in S160 will be described with reference to FIG. In S167, it is determined whether or not a work display operation has been performed. The user displays the normal screen display (see FIG. 24A) from the band menu bar or pop-up menu displayed at the top of the normal screen of the display unit 37 of the client terminal 2, and clicks the “task list button”. Thus, YES is determined in S167, and the control advances to S168. In S168, it is determined whether or not there is a limited selection of work and a plan to which it belongs.

  If the user selects and restricts the work and plan that the user wants to display, the process proceeds to S170 after the process of narrowing the work extraction target to the selection restriction is performed in S169. On the other hand, when the user does not limit the selection of work and plan, the process proceeds to S170 after the process for extracting all work is performed in S176. In S170, it is determined whether or not there is a grace period limitation. When the user restricts the grace period to input, the control proceeds to S171, and a process of extracting work within the grace period that is limited from the extraction targets narrowed down in S169 or S176 is performed. This is a process of extracting work that starts and ends within a limited grace period.

  On the other hand, when the user designates the reference date, the control proceeds to S178, and a process of extracting all the work having the designated date as the reference date from the extraction target is performed. Specifically, all jobs including a reference date designated by the user during the grace period are extracted. Here, the “reference date” is a date that is a starting point for extracting a range to be displayed by the scheduler. Normally, the scheduler determines and confirms the action schedule of the day, so by default, “the day” is “today”, that is, “the date including the current time”. Also, by letting the user specify the “reference date”, the “set reference date” can be set to “virtual today” to check the work or schedule.

  If the grace period is not limited and the reference date is not specified, the control advances to S179, and a process for extracting all jobs having the current date as the reference date from the extraction target is performed. After the processing of S171, S178, or S179, the control proceeds to S172, where it is determined whether or not there is an all-day scheduled display request. Here, “all-day schedule” means a schedule set all day, and means a schedule without a restraint period set with the set date (24 hours) as a grace period (scheduled execution date).

  If the user does not make a request for display of the all-day schedule, control is performed in step S174 so that the extracted work is displayed in a list on the display unit 37 together with the work completion confirmation check box. On the other hand, if the user has requested display of the all-day schedule, in S173, the tasks including the all-day schedule are extracted, displayed in a list on the display unit 37 together with the schedule completion confirmation check box in the order of the schedule date, and the remaining tasks. Then, a control is performed to display them in a list together with a task completion check box. After the control of S173 or S174, the selection item display process of S175 is executed. Details of the selection item display processing will be described with reference to FIG.

  By S180, it is determined whether or not the selection item display operation has been performed. If not, return. If the item that the user wants to display is single-clicked (one-click), YES is determined in S180 and the control advances to S181 to determine whether the item selected by the user's operation such as single-click is a plan or a link to the plan Is done. If the selected item is neither a plan nor a plan link, the process proceeds to S184. If the selected item is a plan or a plan link, the process proceeds to S182, and the selected item of the plan and the link is displayed as an overhead view. It is determined whether or not it has been done. When the bird's-eye view is not displayed, the control proceeds to S183, and a bird's-eye view display process (tree) is performed.

  Control then proceeds to S184, where it is determined whether the selected item is displayed in a simplified manner. If the item selected by the user is displayed in a simplified manner, control for displaying details of the selected item is performed in S185. On the other hand, if the item selected by the user is displayed in detail, control is performed to simply display the selected item in S186.

  In the display process of the selection item, the user selects the item by single-clicking on the screen, and the item is executed (displayed) by double-clicking. The actual display forms of the “simplified display” and “detailed display” differ depending on the display form of the list, calendar, and other actual display screens. In particular, calendar display or the like varies depending on the number of days displayed at one time.

  Next, the flowchart of the subroutine program for the schedule display process shown in S161 will be described with reference to FIG. In S190, it is determined whether or not a schedule display operation has been performed. If the user selects and designates (for example, single click) one of calendar one month, calendar two weeks, calendar one week, or calendar one day in the normal screen (see FIG. 24A) displayed on the display unit 37, In S190, the determination is YES, and the control advances to S191, where calendar display in a range including the reference date is performed in the designated display format (calendar 1 month, 2 weeks, 1 week, or 1 day) (FIGS. 28 to 27). reference).

  The display format and the reference date specified by the user are normally input in the event loop using a mouse or the like. Here, for convenience, it is assumed that the display format and the reference date are specified before calling each display process. Therefore, the reference date has already been set, and the display of the calendar display screen of the scheduler that seems to be normally selectable, such as 1 month (5 weeks), 2 weeks, 1 week, 2 days, 1 day, etc., can also be selected before calling It is assumed that it is set. The “reference date” here is a date guaranteed to be included in the period of the selected display format (1 month (5 weeks), 2 weeks, 1 week, 2 days, 1 day). That is.

  Next, in S192, it is determined whether or not a plurality of dates are displayed as calendars. If a plurality of dates are not displayed on the calendar displayed in accordance with S191, the control proceeds to S194. If a plurality of dates are displayed, whether one of the displayed dates is selected in S193. It is determined whether or not. If the determination result is NO, the process returns. If the determination result is YES, the control proceeds to S194, and a control for displaying the schedule of the selected date and the other schedule on the display unit 37 is performed. In an actual operation, a selection is made by a single click on the screen, and an execution (display) operation is made by a double click.

  Next, a flowchart of a subroutine program of the work schedule simultaneous display process (display of a calendar and a task list in a range linked to the display range) shown in S162 will be described with reference to FIG. By S200, it is determined whether or not a work schedule simultaneous display operation has been performed. If not, return. When the user clicks the “task list calendar simultaneous display button” in the normal screen (see FIG. 24A) displayed on the display unit 37, the determination is YES in S200, and the control proceeds to S201, where the schedule display is performed. Processing (calendar display processing) is executed. By this processing, control is performed to display the display screen selected by the user from the schedule (calendar) display screens of FIGS. 28 to 30B.

  Next, the display state of the calendar is confirmed (S202), and it is determined whether or not the calendar is selected on a date basis (S203). The calendar display screen of the scheduler is one month (five weeks), two weeks, one week, two days, and one day, and has three types: monthly, weekly, and date units. If the selection is made on a monthly or weekly basis, the control advances to S205, and a process of setting the calendar display range as a grace period for limited extraction is performed. On the other hand, if the date is selected, the control advances to S204, and a process of setting the range selected by the user as a work grace period for limited extraction is performed.

  This “selected range” means the range selected by the user on the display screen when the subroutine program of this work schedule simultaneous display processing (display of the calendar and task list in the range linked to the display range) is called. That's it. Next, a task display process (task list) is executed in S206. Details of this processing are shown in FIG. In this task display process (task list), the grace period set in S204 or S205 described above becomes the “specified grace period” in S171, and the tasks within the grace period are extracted, and the extracted task list is displayed. (Task list) is simultaneously displayed on the left side of the calendar displayed in S201 (see FIG. 26).

  In the calendar display area on the right side of FIG. 26, the title of the other-scheduled schedule “first meeting schedule of the graph creation software meeting” is displayed after the name of the other-scheduled schedule “graph creation”. This is a search and display of the work “graph creation” and the schedule “schedule of the first meeting of the graph creation software meeting” stored in association with each other by the path. For example, in the schedule (calendar) 1-week display (see FIG. 30A) described later), the all-day schedule of “graph creation” is displayed, which should be displayed as a task list (task list). In FIG. 30 (a), since only the calendar is displayed, “graph creation” which is scheduled for the whole day is displayed in the calendar. However, when the task list and the calendar display are displayed simultaneously as shown in FIG. 26, the “graph creation” is displayed in the task list without displaying the calendar. Such control is possible because the schedule and other schedule and work are linked and managed in a unified manner, and is an advantage of the unified management.

  Also, tasks that have not yet been scheduled (for example, taking photos and organizing experimental data) are displayed in the task list. If even one task is scheduled, that task disappears from the task list and is calendared. The control displayed on the side is performed. Such control is possible because the schedule and other schedule and work are linked and managed in a unified manner, and is an advantage of the unified management.

  Next, a flowchart of a subroutine program of the overhead view display process (tree) shown in S163 will be described with reference to FIG. In S207, it is determined whether or not a tree display operation has been performed. If there is no tree display operation, the process returns. When the display of the tree screen is executed from the “normal screen” shown in FIG. 15, the determination is YES in S207, the control proceeds to S208, and the display unit 37 displays the tree (see FIG. 17A). ). This tree display process is a display mode in which plans, tasks, and schedules linked and stored by a path are searched and displayed, and these are displayed because they are linked and stored by a path and managed in a unified manner. For example, the work path of “specification creation” is “ROOT / applied research plan / patent acquisition plan / specification creation”, which is connected to ROOT-applied research plan-patent acquisition plan-specification creation1 It is a tree display part of the book. Next, it is determined whether or not there is an operation for ending the overhead view display (S209). If there is no ending operation, the control of S208 is continued, and if there is an ending operation, the process returns.

  Next, various display screens displayed on the display unit 37 of the client terminal 2 and transitions between the display screens will be described with reference to FIGS. First, the transition from the normal screen and the normal screen to another display screen will be described with reference to FIG. A normal screen can be displayed from a band menu bar or a pop-up menu displayed on the display unit 37. On this normal screen, “task list calendar simultaneous display button”, “task list display button”, “calendar one month display button”, “calendar two week display button”, “calendar one week display button” and “calendar one day display button” are displayed. Is done. When the user selects and clicks these various display buttons, display control corresponding to the clicked button is executed as described above.

  Next, as shown in FIG. 15, when the user executes tree display from the normal screen, the screen transitions to a tree display screen, that is, an overhead view display screen. This overhead view (tree) screen is shown in FIG. In addition, when the user executes display of the normal screen from the overhead view display screen, the screen transitions to the normal screen.

  Next, transition from the overhead view (tree) screen to another display screen will be described with reference to FIG. On the bird's-eye view display (tree) screen, for example, as shown in FIG. 17A, items of various plans and various works from the ROOT plan are displayed. In order to transition from the overhead view (tree) screen to another display screen, the user first selects and designates one of the displayed items.

  Specifically, after selecting an existing plan (for example, applied research plan) and clicking Edit from the pop-up menu on the display screen, go to the plan existing edit display screen (see FIG. 19B). Transition. When an existing plan (for example, a ROOT plan) is selected and a new plan is created immediately below the existing plan, the screen changes to a plan new edit display screen (see FIG. 19A).

  When an existing plan (for example, a ROOT plan) is selected and a new job is created immediately below the existing plan, the screen shifts to a new job editing display screen (see FIG. 20A). When an existing plan (for example, an applied research plan) is selected and a new plan is created immediately below the existing plan, the screen changes to a new plan edit display (automatic job generation) screen. This is a screen for automatically generating a direct job since there is no direct job to be newly generated (see S41 to S45). When an existing plan (for example, an applied research plan) is selected and a new creation of another schedule is executed immediately below the existing plan, a transition is made to the other schedule schedule new edit display (automatic work generation) screen. This is a screen for automatically generating a direct job because there is no other directly-directed task that is newly generated (see S100 to S109).

  When editing is executed after selecting an existing job (for example, a patent acquisition plan), the screen shifts to a job existing editing display screen (see FIG. 20B). Via this work existing edit display screen (see FIG. 20 (b)), a transition to the scheduled existing edit display screen, the other schedule existing edit display screen, the other schedule new edit display screen, and the schedule new edit display screen is made. It becomes possible.

  Specifically, when a new schedule is created for an existing job, the screen shifts to a schedule new edit display screen (see FIG. 21A). When a new creation of another schedule is executed for an existing task, the other schedule new edit display screen (see FIG. 22B) is executed. When the editing of the selected existing other-scheduled schedule is executed, the screen transits to the other-scheduled schedule existing edit display screen (see FIG. 23B). When the editing of the selected existing schedule is executed, the screen shifts to the schedule existing editing display screen (see FIG. 22A).

  In FIG. 16, what is indicated as “automatic task generation” automatically generates higher-level tasks based on the schedule or other-scheduled schedule generation information. It is a screen that also displays work generation information. Also, in practice, after the items are corrected and generated, the screen returns to the screen before transition (tree display), but the transition arrows are omitted here to avoid complication of the figure.

  Next, the “overhead display screen” will be described with reference to FIGS. 17 (a) to 18 (b). The “overhead view display screen” includes tree display (see FIG. 17A), icon display (see FIG. 17B), list display (see FIG. 18A), and column display (see FIG. 18B). 4 types are prepared. Any one of four types of overhead view display screens can be selected and displayed according to the user's operation.

  The “overhead display (tree) screen” will be described with reference to FIG. As already described, the database 5 is associated with a tree from the upper item to each lower item, such as a “ROOT plan”, a higher level plan belonging to it, a lower level plan belonging to the higher level plan, and a work belonging to the lower level plan. The tree-like items are displayed on the overhead view (tree) screen.

  All items can be uniquely searched by a hierarchical path starting from a “ROOT plan” that is a plan having an infinite grace period. In other words, all items are included in the “ROOT plan”. In FIG. 17 (a), all plans and tasks are expanded and displayed on the tree. However, since the plan is considered to be a folder in which items below it are stored, each plan is used as a starting point. All the following items can be hidden. For example, if a non-display operation is selected in a pop-up menu after selecting any plan, all items below the selected plan can be hidden.

  In this system, schedules and other schedules are considered as division units of work, and therefore, normally, the detailed display screen is displayed by opening a work without being included in the display items of the tree display as shown in FIG. The schedule will be confirmed and edited. For example, by clicking and opening the job of “specification creation”, the schedule “planning meeting with patent attorney” belonging to the specification creation is displayed and can be confirmed and edited.

  In the example shown in FIG. 17A, there is no mixture of plans and tasks, but a plurality of plans and a plurality of tasks can be mixed in a certain plan. Also, by displaying a new item creation screen after selecting any plan, child plans and child jobs can be created immediately below the selected plan, and can be confirmed and edited on the detailed display screen.

  Next, the “overhead display (icon) screen” will be described with reference to FIG. In FIG. 17B, “ROOT plan” is opened and displayed as an icon, which is the same as the GUI (Graphical User Interface) file operation screen. If you open the "Basic Research Plan", the character string of the band displayed as "ROOT Plan" becomes "Basic Research Plan" and its contents are displayed. A personal computer can be operated by opening a plurality of items. Just as you can open a folder and check the folders and files in it, you can check the plans and tasks that are directly under it. A plan corresponds to a folder, and a task corresponds to a file. However, as already explained, all operations are restricted by the grace period of the upper plan, and the link cannot be created below the entity.

  Next, the “overhead display (list) screen” will be described with reference to FIG. FIG. 18A shows a state in which the “ROOT plan” is opened and displayed as a list, which is the same as the GUI file operation screen. If the “Basic Research Plan” is opened, the character string of the band displayed as “ROOT Plan” becomes “Basic Research Plan” and its contents are displayed in a list. A personal computer can be operated by opening a plurality of items. Just as you can open a folder and check the folders and files in it, you can check the plans and tasks that are directly under it. A plan corresponds to a folder, and a task corresponds to a file. However, all operations are limited by the grace period of the upper plan, and links cannot be created below the entity. The folder's mini icon at the top indicates that it is a plan, and in the case of work it becomes a document's mini icon.

  Next, the “overhead display (column) screen” will be described with reference to FIG. In FIG. 18B, the “ROOT plan” is opened and displayed as a list, which is the same as the GUI file operation screen. In the example of FIG. 18B, since “patent acquisition plan” is selected, a light color is displayed in the “applied research plan” to which it belongs to indicate a pass. If the “Basic Research Plan” is opened, the character string of the band displayed as “ROOT Plan” becomes “Basic Research Plan” and its contents are displayed in a list. A personal computer can be operated by opening a plurality of items.

  Just as you can open a folder and check the folders and files in it, you can check the plans and tasks that are directly under it. A plan corresponds to a folder, and a task corresponds to a file. The folder's mini icon at the top indicates that it is a plan, and in the case of work it becomes a document's mini icon. In the example of FIG. 18B, the plan and work are clearly separated according to the columns such that the plan is up to the second column and the third column is work, but if the plan and work are mixed in the same plan, , The plan is displayed on the same column (for example, the second column), and the work is listed below.

  Next, the “plan new edit display screen” will be described with reference to FIG. This “plan new edit display screen” is an edit display screen when YES is determined in S23 of FIG. The path display area 40 displays a route from the route plan to the immediate parent plan where the new plan is generated. In the example of FIG. 19A, the ROOT plan is selected as a direct parent plan. The path display area 40 displays the path of the item immediately below the ROOT plan. An abbreviation of the plan is input to the plan name input setting area 41, and an outline of the plan is input to the outline input setting area 42, respectively. The completion check box 47 is for the user to check when the plan input in the plan name input setting area 41 is completed.

  The completion check box 47 can be selected as an option to enable or disable the completion check box 47 in a default state. When the completion check box 47 is enabled, the user can manually check the completion check box 47. However, if the lower layer includes any plan or job, the lower layer includes an uncompleted item. A warning message is displayed asking whether or not to complete. When the user ignores the warning and continues the completion, all the incomplete items in the lower layer are checked for completion together with the plan to be edited, and the plan itself is edited as completed. If execution of the completion is canceled according to the warning, the previous editing state in which the completion check was attempted is returned. The completion check box 47 of the plan to be edited is automatically checked when all the subordinate items (tasks and plans) are checked for completion (when the last item is checked for completion). The

  On the other hand, when the completion check box 47 is invalid, the check operation to the completion check box 47 is invalidated when at least one plan or work is generated immediately below the plan to be edited. The completion check box 47 of the plan to be edited is automatically checked when all the subordinate items (tasks and plans) are checked for completion (when the last item is checked for completion). The Here, “invalidation” means a state in which manual editing is impossible, and automatic editing by the system is possible.

  The new plan button 43 is a button that is clicked when the user generates a new plan. The new task button 44 is a button that is clicked when the user creates a new task. The new schedule button 45 is a button that is clicked when the user generates a new schedule. The new irregular schedule button 46 is a button that is clicked when the user creates a new irregular schedule. Since there is no transition from the “planned new edit display screen” to another new edit screen (see FIG. 16), these buttons 43 to 46 are disabled and the button display is dimmed.

  The start input setting area 48 in the “grace period” is an area for inputting the start date of the grace period of the new plan input in the plan name input setting area 41. The end input setting area 49 in the grace period is an area for inputting the end date of the grace period of the new plan input in the plan name input setting area 41. In the case of new editing, the grace period of the immediate parent plan is copied and input as a default value in the start input setting area 48 and the end input setting area 49 of the “grace period”. Can be reduced. In the example of FIG. 19A, since the grace period of the route plan is copied, the minimum infinite value is set for “start” and the maximum infinite value is set for “end”.

  In the “work period”, the time when the work is actually started and the time when the work is finished are set. Specifically, the time when the work is actually started is input to the start input setting area 50, and the time when the work is actually ended is input to the end input setting area 51. In the example of FIG. 19A, the appearance is the same as the “grace period”, but the “work period” is set to a non-set value (such as nil) as an initial value for both “start” and “end”. “Nil” means empty for an Objective-C object (id type). Normally, when the completion check box 47 is checked, the time is automatically set to “end” of the “work period”.

  The plan and work are internally separated from the grace period, and a work period is established. The time when the work is undertaken and the time when the work is started are recorded at the start of the work, and the time when the work is completed is recorded at the end of the work. Manage the actual with the period. The schedule also has work start and work end as times in the inside separately from the restraint period. However, in the case of a normal schedule, since it is a restraint period, it is usually the work start and work end. When the start time of the period elapses, the start time is automatically set to start work, and when the end time elapses, the end time is automatically set to end work. However, in the case of an all-day plan (a plan set for the whole day), the restraint period is ignored and the grace period for each day is activated, so the forecast and the actual are managed according to the work period in the same way as the plan and work default. it can.

  The “plan new edit display screen” explained above is the “plan existing edit display screen”, “job new edit display screen”, “task existing edit display screen”, “schedule new edit display screen”, “schedule new edit display screen (task Common explanation part of "automatic generation) screen" "scheduled existing edit display screen" "other rules schedule new edit display screen" "other rules schedule new edit display (task automatic generation) screen" and "other rules schedule existing edit display screen" There is. In the subsequent various edit display screens, detailed description of the common parts will not be repeated, and different parts will be mainly described.

  The “plan existing edit display screen” will be described with reference to FIG. This “plan existing edit display screen” is an edit display screen when NO is determined in S23 of FIG. In the path display area 40, “/ applied research plan /” is input. Thus, in the example of FIG. 19B, the applied research plan is selected as the direct parent plan. In the plan name input setting area 41, “patent acquisition plan” is input as an abbreviation of the plan, and in the outline input setting area 42, an application for “patent obtainable together with the results of applied research is submitted. , "Obtain a patent." In the example of FIG. 19B, since the existing editing is performed, the current set value is displayed in an editable state. The completion check box 47 has the same function as that of FIG.

  In the case of existing editing, the current setting value is displayed in the “grace period” in an editable state. Therefore, if necessary, it is reset to a more consistent period. In the “work period”, the time when the work is actually started and the time when the work is finished are set. In the example of FIG. 19B, since it is a state before the work starts, an unset value (such as nil) is set as an initial value for both “start” and “end” in the “work period”. Usually, when completion is checked, the time is automatically set to “end” of “work period”. Since the “plan existing edit display screen” may change to another new edit screen (see FIG. 16), the new plan button 43, the new work button 44, the new schedule button 45, and the new other schedule button 46 It is activated (validated), and the button display is darker than in FIG.

  The user displays the contents of the outline displayed in the outline input setting area 42, the contents of the start input setting area 48 and the end input setting area 49 of the grace period, and the start input setting area 48 and the end input setting area of the “work period”. 49 contents can be edited to other contents. However, the contents of the start input setting area 48 and the end input setting area 49 of the grace period can be edited only within the grace period of the “applied research plan” which is a direct plan. Further, the contents of the start input setting area 48 and the end input setting area 49 of the “work period” can be edited only within the range of the displayed period of the start input setting area 48 and the end input setting area 49 as a grace period. It is. As further editing contents, editing for “publishing a specific person or group by setting authority” shown in S27 of FIG. 4A is possible. This “patent acquisition plan” is disclosed to individuals or groups for which authority is set. As a result, the disclosed individual or group can generate this “patent acquisition plan” link (see FIG. 6).

  Next, the “new job editing display screen” will be described with reference to FIG. The “new job edit display screen” is an edit display screen when YES is determined in S33 of FIG. Nothing is displayed in the path display area 40. In this state, the ROOT plan is selected as a direct parent plan. An abbreviation of work is input to the work name input setting area 52, and an outline of work is input to the outline input setting area. Since there is no transition from the “new job edit display screen” to another new edit display screen (see FIG. 16), the new plan button 43, the new job button 44, the new schedule button 45, and the new other schedule button 46 are The button display is dimmed because it is deactivated (invalidated).

  Next, the “work existing edit display screen” will be described with reference to FIG. This “work existing edit display screen” is an edit display screen when YES is determined in S36 of FIG. In the path display area 40, “/ applied research plan / patent acquisition plan /” is input. As a result, the patent acquisition plan directly under the applied research plan is selected as the direct parent plan. In the work name input setting area 52, “Create statement” is input. As a result, an existing job for “specification creation” that is directly under the patent acquisition plan is designated. In the summary input setting area 42, the summary of the existing work of “Create specification” is input, and specifically, “Create a description of the technology that is currently available for patent acquisition” is input. As a result, the user can recognize the contents of the existing job “create statement”.

  In order to edit an existing task, the current setting value of the existing task is displayed in an editable state in the start input setting area 48 and the end input setting area 49 for the grace period. In the “work period” start input setting area 48 and end input setting area 49, the actual work start time and the work end time are set. Since it is in a state before the work starts, an unset value (such as nil) is set as an initial value for both “start” and “end” in the “work period”. Since there are two new edit display screens that can be transitioned from the “existing task edit display screen”, the “schedule new edit display screen” and the “other schedule new edit display screen” (see FIG. 16), the new schedule button 45 is displayed. Also, the display of the new irregular schedule button 46 is displayed darker than that in FIG.

  The user displays the contents of the outline displayed in the outline input setting area 42, the contents of the start input setting area 48 and the end input setting area 49 of the grace period, and the start input setting area 48 and the end input setting area of the “work period”. 49 contents can be edited to other contents. However, the contents of the start input setting area 48 and the end input setting area 49 of the grace period can be edited only within the grace period of the “patent acquisition plan” which is a direct report. Further, the contents of the start input setting area 48 and the end input setting area 49 of the “work period” can be edited only within the range of the displayed period of the start input setting area 48 and the end input setting area 49 as a grace period. It is. As further editing contents, the editing for “publishing a specific individual or group with authority” shown in S37 of FIG. 4B is possible. This “specification creation” job is disclosed to individuals or groups to which authority is set. As a result, the disclosed individual or group can generate a link for this “specification creation” task (see FIG. 6).

  Next, the “schedule new edit display screen” will be described with reference to FIG. This “schedule new edit display screen” is a display screen for newly generating a schedule, and is an edit screen when YES is determined in S48 of FIG. In the path display area 40, “/ applied research plan / patent acquisition plan /” is input. In this state, the “patent acquisition plan” that is directly under the applied research plan is designated as the plan. In the schedule name input setting area 53, the job name of the job to which it belongs is displayed as it is as a schedule name in an uneditable state. In the example of FIG. 21A, “specification creation” is input, and a new schedule with the name “specification creation” is selected as an editing target.

  Although “schedule name” cannot be edited, a feature unique to the schedule can be added as an abbreviation to the title input setting area 54. For example, “scheduled meeting with patent attorney” is input. The title input setting area 54 may be omitted and may be left uninput. Since the outline of the work to which the new schedule is input is copied in the new schedule outline input setting area 42, the user can edit it to make an appropriate sentence if necessary.

  In the case of new editing, the user inputs and sets the date of the scheduled execution date before the new editing display screen is displayed. At that time, the user can input and set the date only within the range of the grace period of the work to which the user belongs (for example, description creation). After that, when the new edit display screen is displayed, the date of the scheduled execution date that has been input and set in advance is displayed in the start input setting area 48 and the end input setting area 49. Further, only the time portion in which the minute portion of the current time is discarded is set as an initial value in the start input setting area 48, and the time after 1 hour has passed in the start input setting area 48 is set in the end input setting area 49. It is set as an initial value. The user changes these times to appropriate values as necessary. When the time is edited by the user, the time can be edited only within the range of the grace period of the work to which the user belongs (for example, description creation).

  In the example of FIG. 21A, since the all-day option is not set, the completion check box 47, the all-day option button 55, the “work period” start input setting area 50, and the end input setting area 51 are not settable (grayed out). ). The “all-day option” is an option for setting “schedule” and “other-day schedule” throughout the day to be “all-day schedule” and “all-day other-day schedule”, respectively. When the user clicks the all-day option button 55 to turn it on, the screen shifts to an “all-day schedule edit display screen” for “schedule” and to an “all-day schedule display screen for all-day schedule” for “other schedule”. This will be described later. In the example of FIG. 21A, since the all-day option is not set, the start input setting area 50 and the end input setting area 51 of the “work period” cannot be edited, but the actual work time is sampled. If so, you may be able to edit it manually.

  Next, the “schedule new edit display (automatic job generation) screen” will be described with reference to FIG. This “schedule new edit display (automatic job generation) screen” is a display screen for newly generating a schedule in a state where a direct job has not been generated, and in the case where NO is determined in S41 of FIG. It is an edit screen. The difference from the “scheduled new edit display screen” in FIG. 21A is that a direct job is automatically generated because there is no direct job.

  In the path display area 40, “/ applied research plan / patent acquisition plan /” is input. In this state, the “patent acquisition plan” that is directly under the applied research plan is designated as the plan. A new job is automatically generated immediately below the “patent acquisition plan”. Specifically, when the user inputs a schedule name (for example, “scheduled meeting with the patent attorney at the fifth meeting”) in the schedule name input setting area 53, the schedule name is automatically generated as it is (for example, “ The schedule name input setting area 53 is an indispensable input item because it cannot be omitted. As described above, input to the title input setting area 54 and the outline input setting area 42 can be omitted.

  In the case of automatic work generation by new editing, the user inputs and sets the date of the scheduled execution date of the schedule before the new editing display (automatic job generation) screen is displayed. At that time, the user can input and set the date only within the range of the grace period of the job to which the user belongs (in this case, automatically generated job). The automatically generated work grace period is set to the initial value (see S44) before editing generated from the grace period of the plan selected as the generation destination described above (patent acquisition plan in the example of FIG. 21B). Is done. After that, when a new edit display (automatic work generation) screen is displayed, a grace period date set in advance is displayed in the start input setting area 48 and the end input setting area 49.

  Further, only the time portion in which the minute portion of the current time is discarded is set as an initial value in the start input setting area 48, and the time after 1 hour has passed in the start input setting area 48 is set in the end input setting area 49. It is set as an initial value. The user changes these times to appropriate values as necessary. When the user edits these times, it can be edited only within the range of the automatically generated work grace period. In the “work period”, the start input setting area 50 and the end input setting area 51 are set with the actual work start time and the work end time.

  In the example of FIG. 21B, since the all-day option is not set, the completion check box 47, the all-day option button 55, the “work period” start input setting area 50, and the end input setting area 51 are not settable (grayed out). ). If the all-day option is set by default, the completion check box 47 and the start input setting area 50 and the end input setting area 51 of the “work period” are enabled, and the set constraint period is disabled. In the example of FIG. 21B, since the all-day option is not set, the start input setting area 50 and the end input setting area 51 of the “work period” cannot be edited, but the actual work time is sampled. If so, you may be able to edit it manually.

  Next, the “scheduled existing edit display screen” will be described with reference to FIG. This “schedule existing edit display screen” is a screen for editing an existing schedule that has already been generated, and is an edit screen when it is determined NO in S48 of FIG. In the path display area 40, “/ applied research plan / patent acquisition plan /” is input. In addition, “Create a statement” is input in the schedule name input setting area 53, and “Fifth meeting schedule of meeting with patent attorney” is input in the title input setting area 54. As a result, the existing schedule with the title “Create a specification” having the title “Schedule of the 5th meeting with the patent attorney” is selected for editing. Although the schedule name input setting area 53 cannot be edited, a feature unique to the schedule can be added to the title input setting area 54 as an abbreviation.

  The user can edit the contents of the outline displayed in the outline input setting area 42 and the contents of the start input setting area 48 and the end input setting area 49 of the restraint period to other contents. However, the contents of the start input setting area 48 and the end input setting area 49 of the restraint period can be edited only within the grace period of “specification creation” which is a direct job. As further editing contents, editing for “publishing a specific individual or group by setting authority” shown in S54 of FIG. 5 is possible. This work is made public to authorized individuals or groups. As described above, input to the title input setting area 54 and the outline input setting area 42 may be omitted. The all-day option is the same as described above.

  Next, the “other rule schedule new edit display screen” will be described with reference to FIG. This “other rule schedule new edit display screen” is a display screen for newly generating another rule schedule, and is an edit screen when YES is determined in S102 of FIG. In the path display area 40, “/ basic research plan / experiment plan /” is input. In the other schedule name input setting area 56, “graph creation” is input. As a result, the new alternative schedule with the name “graph creation” is selected as the editing target. The other-scheduled schedule name displayed in the other-scheduled schedule name input setting area 56 cannot be edited, but a feature unique to the other-scheduled schedule can be added to the title input setting area 54 as an abbreviation. The outline of the work to which the job belongs is copied in the outline input setting area 42, but the user can edit it as necessary to make an appropriate sentence. Note that the title input setting area 54 and the outline input setting area 42 may be omitted.

  In the case of new editing, the user inputs and sets the date of the other schedule before the new editing display screen is displayed. At that time, the user usually inputs and sets a date within a grace period of work to which the user belongs (for example, graph creation). When the user inputs a date that falls outside the grace period range, a warning is displayed (S105). When the user ignores the warning and inputs the date, the input contents are the start input setting area 48 and the end input setting. It is displayed in the area 49 (in the case of YES in S106). Thereafter, at the stage when the other schedule new edit display screen is displayed, the date set in advance is displayed in the start input setting area 48 and the end input setting area 49.

  Further, only the time portion in which the minute portion of the current time is discarded is set as an initial value in the start input setting area 48, and the time after 1 hour has passed in the start input setting area 48 is set in the end input setting area 49. It is set as an initial value. The user changes these times to appropriate values as necessary. Since the new edit display screen does not transit to another display screen (see FIG. 16), the new plan button 43, the new work button 44, the new schedule button 45, and the new other schedule button 46 are disabled (impossible). Have been activated). Further, since the other schedule is newly created, the participation expression button 58 for others to announce participation in the other schedule is disabled (disabled).

  In FIG. 22B, since the all day option is not set, the restraint period is valid. If the all-day option is set by default, the set restraint period becomes invalid. As the usage of the all-day option in other schedules, the date of the event has been decided, but if the holding time is undecided, it will be temporarily set as the whole day, and when the holding time is decided, the all-day setting will be canceled and the restraint period Is normally set.

  Next, the “other schedule new edit display (automatic job generation) screen” will be described with reference to FIG. This “other rule schedule new edit display (task automatic generation) screen” is a display screen for newly generating another rule schedule in a state where no direct task is generated, and it is determined as NO in S100 of FIG. It is an edit screen when it is done. The difference from the “other-schedule schedule new edit display screen” in FIG. 22B is that a direct job is automatically generated because there is no direct job. In the path display area 40, “/ basic research plan / experiment plan /” is input. The other-scheduled schedule name input setting area 56 stands by in a state where input is possible. Since the entered other-scheduled schedule name becomes a work name automatically generated as it is, the input of “other-scheduled schedule name” cannot be omitted and becomes an indispensable input item. As described above, input to the title input setting area 54 and the outline input setting area 42 can be omitted.

  The editing of the restraint period is the same as the description of FIG. 21B, but because it is an edit scheduled for other rules, the warning display (S105) described in FIG. 22B and the user who ignores it Can be set. The all-day option is the same as that described in FIG. In addition, because of the new creation / editing screen, the new plan button 43, the new work button 44, the new schedule button 45, and the new other schedule button 46 are invalidated (disabled).

  Next, the “other schedule existing edit display screen” will be described with reference to FIG. This “other-temporal schedule existing editing display screen” is a screen for editing an existing other-temporal schedule that has already been generated, and is an editing screen when NO is determined in S102 of FIG. In the path display area 40, “/ basic research plan / experiment plan /” is input. Further, “graph creation” is input in the schedule name input setting area 53, and “first meeting schedule of the graph generation software meeting” is input in the title input setting area 54. As a result, the existing other schedule with the title “graph creation” having the title “first meeting schedule of the graph creation software meeting” is selected as the editing target. The other-scheduled schedule name input setting area 56 cannot be edited, but a feature unique to the schedule can be added to the title input setting area 54 as an abbreviation.

  The user can edit the contents of the outline displayed in the outline input setting area 42 and the contents of the start input setting area 48 and the end input setting area 49 of the restraint period to other contents. However, the contents of the start input setting area 48 and the end input setting area 49 of the constraint period can be edited only within the range of the grace period of “graph creation”, which is a direct job. As described above, input to the title input setting area 54 and the outline input setting area 42 may be omitted. The all-day option is the same as described above. As further editing contents, editing for “publishing a specific person or group by setting authority” shown in S108 of FIG. 8 is possible. This other schedule is disclosed to individuals or groups for which authority is set. An individual or a group to whom this other schedule has been made public can participate in this other schedule.

  Specifically, the other person's other schedule is selected and specified on this “other schedule existing edit display screen”, and then the participation expression button 58 is clicked. Thus, YES is determined in S47 and S51 of FIG. 5, and in S52, a process of registering and storing the user who has expressed the participation in the participant list in the other schedule of the generation source is performed. Specifically, in the case of a multi-user environment, when the participation expression button 58 is pressed, a summary in which the character string such as “: attendance” is added to the existing title and the outline and the restraint period are copied as they are belongs. It is automatically generated in the work, and its information is registered in the participant list after the generation.

  In the case of another schedule shown in FIG. 23B, a schedule titled “First meeting schedule of graph creation software meeting: Attendance” is automatically generated. Further, when the new schedule button 45 is pressed, the new schedule edit display screen (see FIG. 21A) is displayed with the same contents. When editing is completed, the restricted period after editing is automatically registered in the participant list. At the same time as the participation in the other schedule (S52), the other schedule becomes the user's own schedule (schedule generated based on the other schedule). The cancellation of participation is performed by deleting the schedule generated due to the other schedule.

  Since other schedules are a special form of schedules, and are different from plans and tasks, links for other schedules cannot be generated like regular schedules. Regarding deletion of a plan or work, when the plan entity is deleted, all the links generated from the entity and all items below the plan are deleted. On the other hand, it is sufficient to delete the link of the plan if the corresponding link itself is deleted. When a work entity is deleted, items such as schedules and other rules are the contents of the work, and there are no items below the work, so it is generated from all the items included in the work and their (entity). It just deletes all the links. As for changes in plans and tasks, the link itself only refers to the entity, so it is only necessary to change the entity, and there is no need to change the link.

  Next, the case where the above-mentioned all-day option is turned on will be described. In each edit display screen shown in FIGS. 21A to 23B, when the user clicks the all-day option button 55, the all-day option is turned on. When the all-day option is turned on, as described above, the screen shifts from the various editing display screens shown in FIGS. 21A to 23B to the corresponding all-day setting screens (not shown). For example, if the all-day option button 55 is clicked on the schedule new edit display screen shown in FIG. 21A, the screen moves to the all-day schedule edit display screen (not shown), and the other schedule new edit display screen shown in FIG. When the all-day option button 55 is clicked, the all-day schedule display screen (not shown) is displayed. The all-day schedule is edited on the all-day schedule editing screen, and the all-day schedule is edited on the all-day other-rule schedule editing display screen.

  When the all-day option is turned on, as described above, the completion check box 47 is activated (activated). In the case of an all-day schedule, the “work period” can be set, and only the date portion of the start input setting area 48 of the restraint period can be edited within the grace period of the work to which it belongs. Is in a non-editable state (grayed out) while displaying the date input in the start input setting area 48 of the constraint period. In addition, the work period start input setting area 50 is set at the start of the work, and the completion check box 47 is checked at the end of the work, whereby the work period end input setting area 51 is recorded.

  In the case of another schedule, by turning on the all-day option button 55, only the date part of the start period setting input area 48 of the restraint period can be edited within the grace period of the work to which it belongs, and the end input setting area 49 of the restraint period is displayed. Is in a non-editable state (grayed out) while displaying the date input in the start input setting area 48 of the constraint period. As the usage of the all-day option in other schedules, the date of the event has been decided, but if the holding time is undecided, once the holding time is determined and the all-day setting is canceled, the restraint period Is normally set.

  Next, the transition within the normal screen display will be described with reference to FIG. As described above, the normal screen is displayed when the user selects and clicks the normal screen from the band menu bar or the pop-up menu displayed on the display screen of the display unit 37 of the client terminal 2. In this normal screen, as shown in FIG. 24 (a), a “task list calendar simultaneous display” button, a “task list” button, and a calendar display mode (four types) for selecting a calendar display mode are displayed. The operation area is displayed. In the “Calendar display” operation area, there are a “Calendar 1 month display” button, a “Calendar 2 week display” button, a “Calendar 1 week display” button, and a “Calendar 1 day display” button. Is displayed.

  When the user clicks the “task list calendar simultaneous display” button, a “task (task list) schedule (calendar) simultaneous display screen” shown in FIG. 26 is displayed. In this state, when the task list full screen display is executed by the user, the task list display screen shown in FIG. 24B is changed from the “task (task list) scheduled (calendar) simultaneous display screen”. A list of tasks of the user is displayed on the task list display screen. In this display state, when the task list calendar simultaneous display is executed by the user, the screen shifts to “task (task list) scheduled (calendar) simultaneous display screen”.

  When the calendar full screen display is executed by the user while the “task (task list) schedule (calendar) simultaneous display screen” or task list display screen is displayed, the “calendar display” operation area is enlarged and displayed. The The “Calendar 1 week display” button, “Calendar 2 week display” button, “Calendar 1 week display” button, and “Calendar 1 day display” button displayed in the “Calendar display” operation area. When the user selects and clicks one of the buttons, the screen is changed to the calendar display screen of the selected mode. When the “Calendar 1 month display” button is clicked, the screen shifts to a schedule (calendar) 1 month display screen shown in FIG. When the “Calendar 2 week display” button is clicked, the screen shifts to a schedule (calendar) 2 week display screen shown in FIG.

  When the “Calendar 1 week display” button is clicked, the screen shifts to a schedule (calendar) 1 week display screen shown in FIG. When the “Calendar 1 day display” button is clicked, the screen shifts to a schedule (calendar) 1 day display screen shown in FIG. Between these schedule (calendar) 1 month display screen, schedule (calendar) 2 week display screen, schedule (calendar) 1 week display screen and schedule (calendar) 1 day display screen, as shown in FIG. The display target changes between the respective display screens according to the user's operation.

  When the work list calendar simultaneous display is executed by the user in a state where the above-mentioned “calendar display” operation area is displayed in an enlarged state or in a state where any of the four modes of the schedule (calendar) display screen is displayed When the task (task list) schedule (calendar) simultaneous display screen is displayed and the task list full screen display is executed, the task display confirmation screen is displayed.

  Next, the work display confirmation screen will be described with reference to FIG. This screen displays a list of user jobs. Specifically, each work name and the due date of the work are displayed in a list, and a completion check box 47 for checking completion of each work is displayed. Originally, the work list in the scheduler is for quickly checking the completion of work, and the completion check box 47 is essential. Therefore, a completion check box 47 for displaying and inputting the presence / absence of completion is displayed at the right end of each work name. In the example of FIG. 24B, the work names “task collection” and “graph creation” are completed.

  In the example of FIG. 24B, the first four task lists counted from the top are displayed in bold font, and the two tasks below are displayed in normal font. The four tasks displayed in bold font are all-day scheduled portions of the task including the all-day schedule. On the other hand, as described above, the scheduled name takes over the work name to which it belongs, that is, the same name, so that each is scheduled for one day. Unlike the normal schedule, the all-day schedule period is not a restraint period but an all-day period, that is, a one-day grace period. Therefore, the scheduled execution date for which the execution time is undecided is displayed as the deadline. The remaining two displayed in the normal font are jobs that do not include any schedule.

  If there is room on the screen, the title of the all-day schedule may be displayed separated by a colon after the job name including the all-day schedule (actually, the scheduled name of the all-day schedule). For example, if the task “collecting issues” includes an all-day schedule with the title “assignment conference 1” and “issue conference 2”, then “issue collection: issue conference 1” 2 ”is displayed. Normally, since a task whose start deadline has passed is extracted and displayed in the task list, the start date of the grace period is only used internally when extracting the task list and is not displayed.

  A display screen that can be changed from the work display confirmation screen will be described with reference to FIG. Based on the user's operation shown in FIG. 25, the task display confirmation screen transits to the existing task edit display screen (see FIG. 20B). From the task existing edit display screen, according to the user's operation, the schedule new edit display screen (see FIG. 21A), the other schedule new edit display screen (see FIG. 22B), the schedule existing edit display screen (See FIG. 22 (a)) or the other-schedule existing edit display screen (see FIG. 23 (b)).

  In addition, after correction and generation of items are completed on the edit display screen of the transition destination, the screen returns to the screen before transition (task list display) according to the user's operation. The arrow of was omitted. Also, if you want to create a new item, call up the tree display. However, it is also possible to create a schedule for an existing job and a new schedule of other rules from the task list display. In addition, there are two methods for reextracting items that are not displayed (extracted) by changing extraction conditions or calling a tree display.

  Next, a work (work list) schedule (calendar) simultaneous display screen will be described with reference to FIG. In the example of FIG. 26, a task list is displayed in the task list column, and a schedule is displayed in the calendar column. In the schedule displayed in the calendar column, specifically, “the first meeting schedule of the graph creation software meeting” held at the time of 13: 00 to 15:00 in the other schedule of “graph creation”. Will attend only between 13:00 and 14:00.

  The task list displayed in the task list column is a completion check list of actions to be executed on that day (February 15, 2016 in FIG. 26) and actions to be executed by the due date. In other words, since it is a list that should be checked and checked on that day, it is most efficient for the calendar to check the schedule of that day. Therefore, by default, the work list and the calendar for the day display are displayed. However, the calendar is changed to one year, one month, two weeks, one week, and one day, and the current situation is grasped by changing the display. It is configured to be easy. Further, if the calendar display form is switched and the reference date is changed, the reference date of the work list is also changed and rewritten to the work list starting from the changed reference date.

  The “task (task list) schedule (calendar) simultaneous display” is a combination of a task (“graph creation” in the example of FIG. 26) and schedule (“graph creation software conference first” in the example of FIG. 26). "Scheduled meeting"). For example, in the schedule (calendar) display for one week (see FIG. 30A)), the all-day schedule of “graph creation” is displayed, which should be displayed as a task list (task list). Since only the calendar is displayed at 30 (a), “graph creation” which is scheduled for the whole day is displayed in the calendar. However, when the task list and the calendar display are displayed simultaneously as shown in FIG. 26, the “graph creation” is displayed in the task list without displaying the calendar. Such control is possible because the schedule and other schedule and work are linked and managed in a unified manner, and is an advantage of the unified management.

  Also, tasks that have not yet been scheduled (for example, taking photos and organizing experimental data) are displayed in the task list. If even one task is scheduled, that task disappears from the task list and is calendared. The control displayed on the side is performed. Such control is possible because the schedule and other schedule and work are linked and managed in a unified manner, and is an advantage of the unified management.

  In addition to work not related to the schedule ("empty work (work that does not hold any schedule)" in this method), it is set all day by using the fact that it is linked to the schedule. By treating a scheduled event (a scheduled date with a set date as a grace period) and not as a schedule, as a division unit for all-day-specified tasks, both empty jobs and all-day schedules are included. It is also possible to manage the list as one work list.

  More specifically, in the present embodiment, an “empty job”, that is, a job that does not include any schedule, is treated as a job that is allowed to be executed within the grace period and is managed for each job. “All-day schedule”, that is, a schedule set all day without restricting the execution time, is restricted with a grace period within the set date (by default, 24 hours from 0:00 of the day to 0:00 of the next day) It is treated as an unset schedule, ie a job with a grace period of 24 hours. Therefore, in addition to being able to display edits linked to tasks and schedules that were impossible in the past, both empty jobs and all-day schedules can be displayed in the task list for a period within the display range, There is an advantage that they can be extracted and generated as a mixed work list and checked for completion in the same list.

  Next, an edit display screen that can transition from the calendar display screen will be described with reference to FIG. Based on the user's operation, as shown in FIG. 24, from the calendar display screen to the existing task edit display screen (see FIG. 20B), the scheduled existing edit display screen (see FIG. 22A), or other schedule existing edit Transition to one of the display screens (see FIG. 23B). Also, from the existing task edit display screen (see FIG. 20B) to the scheduled new edit display screen (see FIG. 21A), the other-scheduled schedule new edit display screen (see FIG. 22B), the other-scheduled schedule existing A transition is made to an edit display screen (see FIG. 23B) or a scheduled existing edit display screen (see FIG. 22A).

  In addition, after correction and generation of items are completed on the edit display screen at the transition destination, the screen returns to the screen before transition (each calendar display) according to the user's operation. The arrow of was omitted. Also, if you want to create a new item, call up the tree display. However, it is also possible to create a schedule for an existing job or a new schedule of other rules from the calendar display. In addition, there are two methods for reextracting items that are not displayed (extracted) by changing extraction conditions or calling a tree display.

  Next, a schedule (calendar) one month display screen will be described with reference to FIG. In the example of FIG. 28, a schedule (calendar) for one month in February 2016 is displayed. In the case of a terminal with a large screen, this one-month display is displayed as much as possible as scheduled to be scheduled for execution on each day from February 1st to 29th, 2016. On a mobile terminal such as a smartphone, The presence or absence of a schedule scheduled to be executed on a day is displayed with an icon or the like. By tapping the icon, the schedule for the day is enlarged. This also applies to the schedule (calendar) two-week display screen of FIG. 29 described later.

  In the example of FIG. 28, the date including the current time is indicated by a thick frame. As another display method, “ToDay” or “Today” may be displayed, or the decoration of the frame may be made special to indicate that the current time is included. This also applies to the schedule (calendar) two-week display screen of FIG. 29 described later. In the example of FIG. 28, only the title is displayed for the schedule with the title set so that as many schedules as possible can be displayed in the frame. Conversely, the schedule is displayed without displaying the title. If only the name is displayed, the schedule of the same genus can be distinguished.

  In this embodiment, as already explained, since a schedule is considered to be a division unit of the work to which it belongs, the name of the schedule is set to the name of the schedule, and all the schedules of the same belonging have the same name. . In this example, the all-day schedule (task collection, graph creation) is displayed, but the character color is displayed in gray to make it easier to distinguish the schedule from the normal time-constrained schedule. Since these schedules are also displayed in the task list, the display on the calendar may be omitted. If the task list is displayed at the same time, it is easier to view the calendar if the calendar is not displayed all day. In the example of FIG. 28, the undecided schedule for the other schedules is in italics (schedule for the third meeting of the assignment meeting), and the other schedules after the participation announcement (schedule generation) is bold (for the first meeting of the graphing software meeting) Planned).

  Next, a schedule (calendar) two-week display screen will be described with reference to FIG. In the example of FIG. 29, a schedule (calendar) for two weeks from February 7 to 20 in February 2016 is displayed. In the example of FIG. 29, the name of the schedule (same as the job name to which it belongs) is displayed, and the title having the title of the schedule following the colon is displayed. In addition, in the example of FIG. 29, the all-day schedule (task collection, graph creation) is displayed, but in order to make it easier to distinguish from a schedule that is restricted by normal time, the text color is displayed in gray and a check box for completion is displayed. Wait at the top. Since these schedules are also displayed in the task list, the display on the calendar may be omitted. If the task list is displayed at the same time, it is easier to view the calendar if the calendar is not displayed all day.

  In the example of FIG. 29, the undecided schedule of the other schedule is in italic font (task collection: schedule of the third meeting of the task meeting), and the schedule of the other schedule after the participation announcement (schedule generation) is bold (graph creation: graph) The first meeting of the created software meeting). Note that the name and title of the participation statement representing the attendance of the other law schedule are omitted, but in the case of a shorter time than the other law schedule (when leaving midway), as shown in FIG. The participation time is displayed in brackets.

  Next, a schedule (calendar) one week display screen will be described with reference to FIG. In the example of FIG. 30A, a schedule (calendar) for one week from February 14 to 17 in February 2016 is displayed. The method for displaying the date including the current time is the same as that described in the plan (calendar) one month display screen of FIG. In addition, in the example of FIG. 30 (a), the all-day schedule (task collection, graph creation) is displayed, but in order to make it easier to distinguish the schedule from the normal time constraint, the character color is displayed in gray and completed. A check box is waiting at the top.

  Since these schedules are also displayed in the task list, the display on the calendar may be omitted. If the task list is displayed at the same time, it is easier to view the calendar if the calendar is not displayed all day. In addition, although the schedule name and title of the participation expression representing attendance of the other law schedule are omitted, in the case where it is shorter than the other law schedule (when leaving in the middle), it is shown in FIG. The participation time is displayed in parentheses as shown. In addition, a schedule having a title may not be set to “schedule name: title” but may be displayed by omitting the schedule name and adding a colon at the head like “: title”.

  Next, a schedule (calendar) daily display screen will be described with reference to FIG. In the example of FIG. 30B, a schedule (calendar) on February 15th, 2016 is displayed. Although the fixed display range is limited, it can be confirmed by displaying the hidden part by scrolling the display screen. In the example of FIG. 30 (b), the all-day schedule is not displayed because it is a day display. However, if the task list is not displayed at the same time, a separate frame is provided on either the top, bottom, left, or right to schedule the all-day schedule. It may be displayed with a check box. The first bold type in FIG. 30B is a schedule of other rules, and the event (the first meeting schedule of the graph creation software meeting) itself is held from 13:00 to 15:00.

  The next normal font character is the schedule of the user who uses the scheduler, and indicates that he / she is participating in the event from 13:00 to 14:00 (withdrawal). Here, “: Attendance” is the suffix of the title attached to the schedule generated due to the other schedule (graph creation: the first meeting schedule of the graph creation software meeting). It is desirable that a predetermined suffix for the title such as “: attendance”, “: participation”, etc. can be set at the time of generation. Also, if you do not leave in the middle, that is, if the other law schedule and the resulting schedule have the same restraint period, either the other schedule or the schedule resulting from it will be hidden, and the schedule with the title will be Instead of “schedule name: title”, the schedule name may be omitted so that only the title can be displayed by adding a colon at the head like “: title”.

  In the embodiment described above, the plurality of client terminals 2... Shown in FIG. 1 are shown to operate as a client / server model. However, as a modified example, a plurality of client terminals 2. Explain what works standalone. In this modification, only differences from the above-described client / server model will be described.

  First, a flowchart of a main routine program executed in the client terminal 2 and the management server 4 will be described with reference to FIG. The difference from the flowchart of FIG. 3B is that a local data display process of S210 is added as a process of the client terminal. This local data display process is a process in which the user displays local private management data on the display unit 37 of his / her client terminal 2 for reference. Details are omitted.

  Next, a subroutine program flowchart of the data editing process of S2 and the data editing corresponding process of S4 will be described with reference to FIG. The difference from the flowchart of FIG. 3C is that a server synchronization process of S215 is added as a data editing process, and a server synchronization support process of S216 is added as a data editing support process. Details of both the processes will be described with reference to FIG.

  FIG. 32 shows a flowchart of subroutine programs of server synchronization processing (S215) on the client terminal side and server synchronization handling processing (S216) on the management server side. When the user operates the client terminal 2 to request server synchronization, a synchronization request signal is transmitted to the management server 4 in S220. The management server 4 that has received it in S221 determines whether or not an item has been changed since the previous synchronization (S222). If the item has not been changed, the control proceeds to S226, and the synchronization result is transmitted to the client terminal 2. In this case, the reply is that there is no item change, and the client terminal 2 receives it (S227), and displays “no item update” on the display unit 37.

  On the other hand, if there is a change in the item, YES is determined in S222, and in S230, the user is allowed to select which update is to be adopted, and the selected one is set as an update item. As a specific method for the user to select, a selection screen is transmitted from the management server 4 to the client terminal 2, and the user who sees the selection screen displayed on the display unit 37 performs a selection operation, and the selection result signal Is returned to the management server 4. Control then proceeds to S224, where it is determined whether the update item is on the client terminal side. In the case of the client terminal side, a process of rewriting the management server side item with the update data of the client terminal side item is performed.

  On the other hand, if the update item is on the management server side, processing of rewriting the client terminal side item with the update data of the management server side item is performed in S231. Next, the control advances to 226, and the synchronization result is transmitted to the client side. The client terminal 2 receives it (S227), and a process of updating the private management data local to the client terminal 2 is performed through S229.

Next, the feature points and modifications of the embodiment described above will be listed.
(1) In the above embodiment, the project manager can grasp the detailed progress including the non-administrator's action schedule by centrally managing and coordinating the plan / work / plan.

(2) Task lists (task lists) and calendars (schedules), which have conventionally been separated and independent, can be linked and linked as a job execution grace period and an execution scheduled date and time (execution constraint period).

(3) Since the other schedule is a reference information and does not restrict its own actions, it exists independently like a memo within the work to which it belongs, so it is not subject to the grace period of the work to which it belongs ( (See FIG. 8). In other words, unlike normal schedules, it can be generated beyond the grace period of higher-level work and plans.

(4) Also, within the grace period of the work to which it belongs, by generating the work that belongs to the schedule that expresses the participation from the other schedule, it is possible to It becomes possible to link the participation schedule to the event. For example, suppose that Taro is planning to attend a product planning briefing event held on the day of the month. In the product plan briefing session, data is stored in the form of a time table in which a plan presentation is given from 10:00 to 12:00 and a specific product is explained from 13:00 to 14:00.

  For example, Jiro who browsed the time table as a reference item can make only his / her plan as a plan to participate in other rules, for example, from 10:00 to 12:00. In other words, it is possible to refer to other schedules made up of timetables as memos, pick up only the items of interest from them, and incorporate them into their schedules. In this way, it becomes possible to link the time table of other events (other events schedule) and the participation schedule to the event. However, the range that can be linked is limited within the grace period of the work to which it belongs (S51).

  In other words, if there is an event already registered as another schedule, if you specify it and create a schedule for the job to which it belongs, you can generate a schedule using the other schedule as a template for schedule management, In terms of project management, it is possible to express participation in the event. It should be noted that generating a schedule using the other schedule as a template is not limited to a general event, and can correspond to any event such as a school timetable or a train timetable.

(6) A shared other schedule (for example, the third meeting schedule 20 of the task meeting in FIG. 1) is generated from the shared work (for example, task collection 19 in FIG. 1) in the project (plan), and the shared By generating individual schedules from other schedules, it is possible to manage the date and participation statement. The shared work is, for example, a meeting.

  Also, when displaying the other person's schedule published in the server application on their own terminal, or when importing data into the local standalone application, the published schedule of the other person was converted to a different schedule. By importing things and displaying them as other people's action timetables, it is possible to propose schedule generation and sharing work based on other people's action schedules, so it is not limited to administrators as in the past It is possible to use it as a communication tool for adjusting the schedule with all members who share the same project (plan). Also, when it is clear that you want to take action with another person, it is convenient to convert the other person's schedule as your own schedule.

  In addition, since a time table related to any event can be held as reference information, a time table of an event closely related to the time schedule can be referred to at the same time, apart from its own action schedule. The event time table includes, for example, an event start time, an end time, and details thereof, a train departure time, an arrival time, details thereof, and the like.

(7) The fact that a certain work is related to a plurality of other plans frequently exists in reality. In addition, by making it belong to a plurality of plans, it is possible to cope with schedule management by context (situation).

  For example, managing actual work (execution) while managing the main plan, and combining work links as a single plan with situations common to multiple plans (using the same equipment or the same execution location etc.) It is possible to efficiently allocate the scheduled execution time.

(8) When creating a link for a plan or task, the grace period of the plan of the link creation destination can include the grace period of the entity, and the creation destination plan does not exist below the plan to which the entity belongs. Only allow link generation. If the grace period is the same, it is considered that it can be included. Below the plan to which the entity belongs is that the link cannot be created in the same plan as the entity.

  Unlike general file and folder links, both the plan and work have a grace period, and if the impact is a plan, the child plan and the included work can only be generated within the grace period. There are restrictions. Moreover, even if the grace period is within the range, it cannot be generated below the plan that is the entity of the link source because the circular reference breaks the hierarchical relationship and causes inconsistency.

(9) When performing scheduling, it is common to first set a goal along the time axis to generate a milestone. Software that supports generation of the milestone may be provided to generate milestone data, and scheduling may be performed using the data as a template. By doing so, there is an advantage that scheduling becomes easy.

(10) In the above embodiment, the management data is stored in not only the database 5 but also in the client terminal 2 in the above embodiment, so that the management server 4 is accessed when browsing only the management data. It is possible to browse the client terminal 2 alone without doing so. However, the management data may be stored only in the database 5 without being stored in the client terminal 2 itself. In that case, in the server data display process shown in S1, the management data to be displayed is transmitted from the management server 4 to the client terminal 2 and displayed.

(11) Although the management server 4 is provided in the above embodiment, the management server 4 may be configured only by a stand-alone user terminal (for example, a personal computer or a smartphone). In that case, if you want to share your own management data stored in the user terminal with others, you can manage by transmitting and receiving the management data you want to share between user terminals by P2P (peer-to-peer) etc. Share data.

(12) The list of various jobs may be controlled to be displayed in the order in which the end of the grace period is approaching. In addition, the list of various plans stored in the database 5 may be controlled to be displayed in the order in which the end of the grace period is approaching.

(13) In the above embodiment, the schedule is displayed in the calendar display (see FIG. 26, FIG. 28 to FIG. 30B), but the work to which the schedule belongs by clicking the displayed schedule. , It may be controlled so that all the plans to which the job belongs are displayed. For example, as shown in FIG. 14, control is performed so that a tree is displayed together with a grace period.

(14) Although the start date and time and end date and time are input as the scheduled restraint period (for example, see FIG. 21A), only the start date and time may be input. Moreover, although the start date and time and the end date and time are input as the grace period of work and plan (see, for example, FIGS. 19 and 20), only the start date and time or the end date and time may be input.

(15) In the above-described embodiment, the items related to the user's work in the company or the like are input as the performance related items related to the items to be performed by the user. However, the present invention is not limited thereto. It is also possible to input and manage performance-related items other than work such as user learning plans and life plans.
(16) The following invention is described in the above embodiment.

  For example, when a plurality of users (for example, employees) manage a business such as a plan, a job, or a schedule in an organization such as a company, a user records the business of another user as reference information. Sometimes you want to. For example, when user A who belongs to the sales department visits a customer, he often hears a complaint about a new product, and when a schedule for collecting a problem and collecting a problem based on the series of complaints is input In addition, there is a case where the user B of the development department in charge of new product development is interested in the task collection task and the task conference schedule and wants to record them as reference information.

In addition, the user A can hear the problem about the new product directly from the customer, and the user B is in a position to use the problem about the new product directly heard from the customer for the next new product development. Therefore, better results can be expected if the two work together in the task of task collection and the task conference. Therefore, if an agreement is obtained between the task collection task and the parties involved in the task meeting, it may be desired to make those tasks common to user A and user B.
The present invention has the following invention specific matters to meet the above-mentioned needs.

Management of matters related to performance to be achieved within a predetermined period (for example, assignment collection 19 in FIG. 1, specification preparation 24, third meeting schedule 20 of the meeting, fifth schedule 25 of the meeting with the patent attorney) Computer system,
Storage means (for example, S35 in FIG. 4B, S50 in FIG. 5) for storing performance-related items of a plurality of users;
Browsing means (for example, S116 and S117 in FIG. 9 and S150 to S155 in FIG. 10) that are the performance-related items stored in the storage means and that can be viewed by other users.
Reference storage means (for example, S118 to S123 in FIG. 9) for storing as a memo to refer to the scheduled items of other users browsed by the browsing means.

  According to such a configuration, if there is a performance-related item that the user wants to browse and refer to performance-related matters of other users, it can be stored as a memo so that it can be referred to later, which improves user convenience. .

  Also, by participating in the schedule items of the other users stored by the reference storage means, generating and registering the schedule items of the schedule related to the performance items of the other users corresponding to the schedule items of the other users A self-schedule generation registration unit may further be provided.

  According to such a configuration, when oneself wants to participate in another user's schedule and wants to make his / her schedule, he / she is the schedule of his / her performance related items corresponding to the schedule of the other user. Scheduled items can be generated and registered, improving user convenience.

  Moreover, you may further provide the change prohibition means which prohibits the change of the said own schedule matter produced | generated and registered by the said own schedule production | generation registration means.

According to such a configuration, it is possible to prevent inconvenience of arbitrarily changing a common schedule item in which not only the user but also other users are participating.
(17) The following invention is further described in the above embodiment.

  When a user (for example, an employee) manages execution-related matters such as a plan, a job, or a schedule, there is a case where a job belonging to a certain plan is desired to belong to another plan. For example, when a job that takes a photograph of an experiment result as a job belonging to the experiment plan is input and managed, there is a case where it is desired to take a picture of the malfunction of the new product as a plan to solve the problem of the new product. . In such a case, there is a demand for managing “photographing” already input as work belonging to the experiment plan as work belonging to “problem solving plan”.

  In addition, the plan includes a higher level plan and a lower level plan belonging to it. For example, with respect to a higher-level plan called “applied research plan”, a “subject solution plan”, a “patent acquisition plan”, etc. can be considered as specific lower-level plans for achieving the plan. When managing a hierarchical plan to which a lower level plan belongs to such a higher level plan, there is a case where it is desired that a plan belonging to a certain plan also belongs to another plan. For example, there is a case where a “personal selection plan” belonging to the “basic research plan” is to be managed as a plan belonging to the “applied research plan”.

In other words, when managing hierarchical execution-related items such as a higher-level plan, a lower-level plan belonging to it, and a job belonging to it, a lower-level performance-related item belonging to a certain higher-level performance-related item is changed to another performance-related item. There is a need to make it belong and manage.
The present invention has the following invention specific matters to meet the above-mentioned needs.

Execution-related items that are to be achieved within a given period and to which one or more lower-level performance-related items belong to the higher-level performance-related items (for example, the plan and work in FIG. 1) A computer system capable of managing
Input means (for example, input operation) capable of inputting the upper first performance related items (experiment plan 9 in FIG. 1) and the lower second performance related items (photographing in FIG. 1) belonging to the first performance related items. Unit 38, the plan input process of FIG. 4A, the work input process of FIG. 4B),
Storage means (for example, S25 in FIG. 4 (a), S35 in FIG. 4 (b)) that stores the first performance-related items and the second performance-related items input by the input means in association with each other is provided. ,
The input means uses a third performance-related item different from the first performance-related information to link the second performance-related matter (for example, the photograph (link) 21 in FIG. 1) stored in the storage means. (For example, the problem solving plan 11 in FIG. 1) can be input (for example, S80 in FIG. 6),
The storage means stores the link of the second performance-related item input by the input means as belonging to the third performance-related item (for example, link generation processing in FIG. 6), a computer system.

  According to such a configuration, a specific performance-related item can be managed by belonging to a plurality of performance-related items at the same time, and the convenience for the user is improved.

  Further, when the hierarchy level of the second performance-related item input by the input means is lower than the hierarchy level of the second performance-related item, the storage means stores the link of the second performance-related item. An abnormality processing means (for example, S85 and S82 in FIG. 6) that performs the abnormality processing without performing the processing may be further provided.

  According to such a configuration, it is possible to prevent an inconvenience that a contradiction that a link of the same performance-related items as that of the performance-related items exists below a certain performance-related items.

[1] A storage means (for example, the database 5) capable of storing performance-related items (for example, plan items, tasks, schedules) related to the items to be performed by the user and the execution time thereof;
The work items (for example, preparation of the specification in FIG. 1) included in the higher-level performance-related items (for example, plan items, tasks) and the lower-level performance-related items (for example, schedules) necessary to specifically execute the job items ) (For example, the fifth meeting schedule 25 of the meeting with the patent attorney in FIG. 1) can be input, and the execution time of the work item and the user's constraint that is the execution time of the schedule item An input means (for example, the input operation unit 38) capable of inputting a period;
In a state where the work item and its execution time are stored in the storage unit, it is determined whether the constraint period of the scheduled item input by the input unit is consistent with the execution time of the work item. Determining means (for example, determining means 72 in FIG. 2),
Storage means for controlling the storage means, the storage means for storing the input schedule item and its restraint period in the storage means, and the input schedule item and a work item that is related to the higher level execution. And a processing unit (for example, the processing unit 73, CPU 30, S50 in FIG. 2) that is stored in the storage unit in cooperation with each other so that they can be managed in a unified manner,
The processing means includes
When the determination means determines that they are not consistent, the storage process is prohibited (for example, NO in S46, S43),
In a state in which the scheduled items input as the user's own performance-related items and the work items that are the immediate higher-level performance-related items are linked and stored in the storage means, the work items are directly related to the higher-level performance-related items. The scheduled items as the performance-related items of the user who is the same person as the user and the constraint period thereof are newly inputted, and The computer system also prohibits the storage process even when the newly input constraint period overlaps (eg, NO in S42, S43).

[2] A storage means (for example, the database 5) capable of storing performance-related items (for example, plan items, tasks, schedules) related to the items to be performed by the user and the execution time thereof;
The work items (for example, preparation of the specification in FIG. 1) included in the higher-level performance-related items (for example, plan items, tasks) and the lower-level performance-related items (for example, schedules) necessary to specifically execute the job items ) (For example, the fifth meeting schedule 25 of the meeting with the patent attorney in FIG. 1) can be input, and the execution time of the work item and the user's constraint that is the execution time of the schedule item An input means (for example, the input operation unit 38) capable of inputting a period;
In a state where the work item and its execution time are stored in the storage unit, it is determined whether the constraint period of the scheduled item input by the input unit is consistent with the execution time of the work item. Determining means (for example, determining means 72 in FIG. 2),
On the condition that it is determined by the determination means that it is consistent, the inputted schedule item and its restraint period are stored in the storage means, and the inputted schedule item and work that is related to the higher level performance Processing means (for example, the processing means 73 and CPU 30 in FIG. 2) that are stored in the storage means in cooperation with each other so that the items can be managed in an integrated manner,
The storage means can store performance related items of a plurality of users (for example, Taro, Hanako ... can store performance related items of Jiro),
The processing means includes reference storage processing means (for example, S104 in FIG. 8) that is stored in the storage means as a memo in order to refer to schedule items of other users that are performance-related items stored in the storage means. Including
The input means participates in the schedule items of the other user stored in the storage means (for example, S52 in FIG. 5), with schedule items of his / her performance related items corresponding to the schedule items of the other user. Including own schedule generation input means (for example, S40 to S42, S46 to S49 in FIG. 5) for generating and inputting a certain own schedule item,
The processing means performs a self-scheduling storage process in which the self-scheduled item and the work item executed by the self-scheduled item are linked and stored in the storage unit so as to be managed in a unified manner (for example, S50), system.

[3] In addition to the invention-specific items described in [2] above, the schedule items of the other users include a time table in which time is allocated for each of a plurality of contents (for example, an event such as a product planning briefing session, a school Timetable, train timetable) data,
The self-schedule generation input means can select the content that the user wants to participate from among the plurality of contents by referring to the data of the time table and input it as the self-schedule item.

  [4] In addition to the invention specific matter described in [2] or [3] above, at the time of entry of the own schedule item by the own schedule generation input means (for example, when YES is determined in S47 of FIG. 5) In the case where it is determined by the determination means that the restraint period of the self-scheduled item is not consistent with the execution time of the work item (for example, when NO is determined in S51 of FIG. 5), An abnormality processing means for performing abnormality processing without performing the own schedule storage processing is further provided (for example, S43 in FIG. 5).

  [5] In addition to the invention specific items described in any one of [1] to [4] above, the work items and the scheduled items that the storage unit stores in cooperation with each other (for example, FIG. 1) The related display means (for example, S200 to S206 in FIG. 14A, S207 to S209 in FIG. 14B, and “Work ( “Task list) plan (calendar) simultaneous display”, and a bird's-eye view display (tree) in FIG. 17A).

  [6] In addition to the invention specific item described in [5] above, the related display means displays a part of the execution time of the work item as a constraint period of the scheduled item (for example, FIG. (February 15, 2016, 13: 00-14: 00 on "task list) plan (calendar) simultaneous display").

[7] In addition to the invention-specific items described in any one of [1] to [6] above, the higher-level performance-related items include plan items established for achieving a certain purpose (for example, FIG. Further includes a patent acquisition plan 12),
The processing means associates the plan item with a work item necessary for concretely executing the plan item in the storage unit by using a path which is a character string for specifying the location of data in the computer. Path association storage processing means for storing,
The path association storage processing means replaces the path following the plan item (eg, plan A in FIG. 2) with the path (eg, / ROOT plan / plan A in FIG. 2) of the work item (eg, job C in FIG. 2). By defining as / work C /), the plan item and the work item are made into tree-structured data (for example, tree data of plan A, job C, schedule D and E in the database 5 in FIG. 2). Store in the storage means.

[8] In addition to the invention specific item according to [7] above, the related display unit displays a tree display unit (for example, a tree display of the plan item and the work item based on the data of the tree structure (for example, 17 (a)),
The input means is a new performance-related item related to the selected performance-related item when the user selects one of the performance-related items including the plan item and the work item displayed by the tree display unit as a cooperation target. Can be generated and input (for example, screen transition from “tree display” in FIG. 16).

[9] In addition to the invention specific items described in any one of [1] to [8] above, the input means includes a first performance related item (for example, experiment plan 9 in FIG. 1) and the first performance related item. When the second performance related item (for example, the photograph 13 of FIG. 1) related to the item is associated and stored in the storage means (for example, S25 of FIG. 4A, FIG. 4B). S35), the second execution related item link can be input as related to a third execution related item (for example, the problem solving plan 11 in FIG. 1) different from the first execution related item (for example, , S80 in FIG.
The processing means stores the link of the second performance related item input by the input means in the storage means in association with the third performance related matter (for example, link generation processing in FIG. 6).

[10] A storage means (for example, the database 5 in FIG. 1, the EEPROM 33 in FIG. 3A) and a processor (for example, FIG. a) CPU 30),
The processor is
The work items (for example, preparation of the description in FIG. 1) included in the higher-level performance-related items (for example, planning, work) and the lower-level performance-related items (for example, schedule) necessary for specifically executing the work items And the input of the schedule item (for example, the fifth conference schedule 25 of the meeting with the patent attorney in FIG. 1), the execution time of the work item, and the user's restraint period that is the execution time of the schedule item, Processing for receiving the input (for example, S30, S40, etc.);
In the state where the work item and its execution time are stored in the storage means, it is determined whether or not the constraint period of the scheduled item received by the receiving process is consistent with the execution time of the work item Processing (for example, S46),
The storage unit stores the received scheduled item and its restraint period in the storage unit, and the storage unit stores the input scheduled item and the work item which is a higher-level execution related item so as to be managed in an integrated manner. Processing to be stored in the means (for example, S50);
The storage process is prohibited when it is determined by the determination means that they are not consistent (for example, NO in S46, S43), and the scheduled item input as the user's own performance-related item and the immediate higher-level performance-related In a state in which the work items that are matters are linked and stored in the storage means, the work items that are the same person as the user and that are scheduled matters that define the work items as directly related to the higher performance When a schedule item as a related matter and its restraint period are newly input, even when the constraint period of the already stored schedule item and the newly entered constraint period overlap, A computer system that executes a storage prohibition process that prohibits a storage process (eg, NO in S42, S43).

[11] Work items (for example, preparation of the specification in FIG. 1) included in the high-level execution related items (for example, plan items, work) related to the items to be performed by the user, and the work items are specifically executed. The input of the schedule item (for example, schedule 5 of the meeting with the patent attorney in FIG. 1) as the necessary subordinate execution related items (for example, schedule) is received, A receiving step (for example, S30, S40, etc.) for receiving an input of a user's restraint period, which is the execution time of the scheduled item,
In a state where the work item and the execution time thereof are stored in the storage means, it is determined whether or not the constraint period of the scheduled item received by the receiving step is consistent with the execution time of the work item. A step (eg, S46),
The step of managing the storage by the storage means, the storage means for storing the accepted scheduled items and the restraint period thereof in the storage means, the work items that are the input scheduled items and the higher-level execution related items And a processing step (for example, S50) that stores the data in the storage unit in cooperation so that they can be managed in a unified manner,
The processing step includes
When it is determined in the determining step that the conditions are not matched, it is determined that the storage prohibition condition is satisfied, and the storage process is prohibited (for example, NO in S46, S43),
In a state in which the scheduled items input as the user's own performance-related items and the work items that are the immediate higher-level performance-related items are linked and stored in the storage means, the work items are directly related to the higher-level performance-related items. The scheduled items as the performance-related items of the user who is the same person as the user and the constraint period thereof are newly inputted, and Even if the newly input constraint period overlaps, it is determined that the storage prohibition condition is satisfied, and the storage processing is prohibited (for example, NO in S42, S43).

[12] Work items (for example, preparation of the description in FIG. 1) included in the high-level execution-related items (for example, plan items, tasks) related to the items to be performed by the user, and specifically execute the job items The input of the schedule item (for example, schedule 5 of the meeting with the patent attorney in FIG. 1) as the necessary subordinate execution related items (for example, schedule) is received, A receiving step (for example, S30, S40, etc.) for receiving an input of a user's restraint period, which is the execution time of the scheduled item,
In a state where the work item and its execution time are stored in the storage means, it is determined whether or not the constraint period of the scheduled item received by the receiving process is consistent with the execution time of the work item. A step (eg, S46),
The step of managing the storage by the storage means, the storage means for storing the accepted scheduled items and the restraint period thereof in the storage means, the work items that are the input scheduled items and the higher-level execution related items And a processing step (for example, S50) for storing the data in the storage unit in cooperation with each other so that they can be managed in a unified manner,
Let the computer execute the processing steps
The storage process is prohibited when it is determined by the determining step that they are not consistent (for example, NO in S46, S43),
In a state in which the scheduled items input as the user's own performance-related items and the work items that are the immediate higher-level performance-related items are linked and stored in the storage means, the work items are directly related to the higher-level performance-related items. The scheduled items as the performance-related items of the user who is the same person as the user and the constraint period thereof are newly inputted, and The storage processing is prohibited even when the newly input constraint period overlaps (for example, NO in S42, S43).

[13] A storage means (for example, the database 5 in FIG. 1, the EEPROM 33 in FIG. 3A) and a processor (for example, FIG. a) CPU 30),
The processor is
The work items (for example, preparation of the description in FIG. 1) included in the higher-level performance-related items (for example, planning, work) and the lower-level performance-related items (for example, schedule) necessary for specifically executing the work items And the input of the schedule item (for example, the fifth conference schedule 25 of the meeting with the patent attorney in FIG. 1), the execution time of the work item, and the user's restraint period that is the execution time of the schedule item, Processing for receiving the input (for example, S30, S40, etc.);
In the state where the work item and its execution time are stored in the storage means, it is determined whether or not the constraint period of the scheduled item received by the receiving process is consistent with the execution time of the work item Processing (for example, S46),
The received scheduled item and its restraint period are stored in the storage means on the condition that it is determined to be consistent by the determination process, and the inputted scheduled item and its higher performance related item are stored. Executing a process (for example, S50 etc.) for storing the work items in association with each other so that the work items can be centrally managed;
The storage means can store performance related items of a plurality of users (for example, Taro, Hanako ... can store performance related items of Jiro),
The process to be stored is a reference storage process (for example, S104 in FIG. 8) that is a performance-related item stored in the storage unit and is stored in the storage unit as a memo to refer to another user's scheduled item. Including
The accepting process is performed by participating in the schedule items of the other user stored in the storage means (for example, S52 in FIG. 5) with schedule items of his / her performance related items corresponding to the schedule items of the other user. Including a self-schedule generation operation acceptance process (for example, S40 to S42 and S46 to S49 in FIG. 5) for accepting an operation to generate and input a certain self-schedule item,
The process to be stored includes a self-scheduled storage process (for example, S50) for storing the self-scheduled item and the work item executed by the self-scheduled item in the storage unit in cooperation with each other so that they can be managed in an integrated manner. Computer system.

[14] The work items (for example, the specification creation in FIG. 1) included in the high-level performance related items (for example, plan, work) related to the items to be performed by the user, and the work items are specifically executed. In addition to receiving an input of a schedule item (for example, schedule 5 of a meeting with the patent attorney in FIG. 1) as a subordinate performance-related item (for example, schedule) required in the above, A reception step (for example, S30, S40, etc.) for accepting an input of a user's restraint period, which is the scheduled item execution time;
In a state where the work item and its execution time are stored in the storage means, it is determined whether or not the constraint period of the scheduled item received by the receiving process is consistent with the execution time of the work item. A step (eg, S46),
The received scheduled item and its restraint period are stored in the storage means on the condition that it is determined to be consistent in the determining step, and the inputted scheduled item and its higher performance related item are stored. A step (for example, S50 or the like) of storing in the storage means in a linked manner so that work items can be managed in an integrated manner,
Let the computer run,
The storage means can store performance related items of a plurality of users (for example, Taro, Hanako ... can store performance related items of Jiro),
The storing step includes a reference storing step (for example, S104 in FIG. 8) that is stored in the storage unit as a memo in order to refer to the scheduled items of other users, which are performance-related items stored in the storage unit. Including
The accepting step includes generating a self-scheduled item that is a schedule item of a performance related item corresponding to the schedule item of the other user by participating in the schedule item of the other user stored in the storage unit. A self-schedule generation operation reception step (for example, S40 to S42 and S46 to S49 in FIG. 5) for receiving an input operation;
The step of storing includes a self-scheduling storage step (for example, S50) in which the self-scheduled item and the work item executed by the self-scheduled item are linked and stored in the storage unit so that they can be managed in a unified manner. program.

  As mentioned above, although embodiment of this invention was explained in full detail, this invention is not limited to these embodiment, A various change is possible in the range which does not deviate from the meaning of this invention.

2 Client terminal 4 Management server 5 Database 8 Applied research plan 11 Problem solution plan 19 Problem collection 20 Scheduled third meeting schedule 30 CPU
36 Communication unit 37 Display unit 38 Input operation unit

Claims (1)

Storage means capable of storing performance-related items and timing related to items to be performed by the user;
It is possible to input the work items included in the high-level performance-related items and the schedule items as the low-level performance-related items necessary for concretely performing the work items, and the execution time of the job items and the schedule items Input means capable of inputting the user's restraint period, which is the execution time of
In a state where the work item and its execution time are stored in the storage unit, it is determined whether the constraint period of the scheduled item input by the input unit is consistent with the execution time of the work item. Determination means to perform,
Storage means for controlling the storage means, the storage means for storing the input schedule item and its restraint period in the storage means, and the input schedule item and a work item that is related to the higher level execution. And a processing unit that stores the data in the storage unit in cooperation with each other so that they can be managed in a unified manner,
The processing means includes
Prohibiting the storage process when it is determined by the determination means that they are not consistent,
In a state in which the scheduled items input as the user's own performance-related items and the work items that are the immediate higher-level performance-related items are linked and stored in the storage means, the work items are directly related to the higher-level performance-related items. The scheduled items as the performance-related items of the user who is the same person as the user and the constraint period thereof are newly inputted, and A computer system that prohibits the storage process even when the newly input constraint period overlaps.