JP6945040B1 - Calendar cooperation system and calendar cooperation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a calendar cooperation system and a calendar cooperation method capable of supporting appropriate implementation of a schedule. A calendar linkage system that links a first calendar system that manages a first schedule and a second calendar system that manages a second schedule for the purpose of managing the execution history of the schedule is a calendar linkage system of the first schedule. Based on the attribute information of the first schedule, the first schedule to be managed by the second calendar system is specified as a shared schedule, and the shared schedule is registered in the second calendar system as the second schedule. A control unit and a control unit are provided. The control unit provides a template to be used in the shared schedule. [Selection diagram] Fig. 1

Description

The present invention relates to a calendar cooperation system and a calendar cooperation method.

In recent years, there has been known a technique for synchronizing schedules registered in each calendar system by linking two types of calendar systems.

Specifically, the first calendar client sends the sharing schedule registered in the first calendar client to the second calendar client, and the second calendar client sends the sharing schedule sent from the first calendar client to the second calendar. Register with the client.

Further, the first calendar client sends the updated sharing schedule to the second calendar client when the sharing schedule is updated, and the second calendar client is the second calendar client based on the updated sharing schedule. Update the sharing schedule registered in (for example, Patent Document 1).

Special Table 2018-501589

In the mechanism described above, the schedule registered in the calendar system is only used for confirming the date and time.

However, in fields such as HR (Human Resource) Tech, it is necessary to confirm whether personnel-related schedules such as goal management and evaluation interviews have been properly implemented.

Therefore, the present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide a calendar cooperation system and a calendar cooperation method capable of supporting appropriate implementation of a schedule.

The calendar cooperation system according to the first feature links the first calendar system that manages the first schedule and the second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule. The calendar cooperation system specifies the first schedule to be managed by the second calendar system as a shared schedule from the first schedule based on the attribute information of the first schedule, and the shared schedule is defined as the shared schedule. As a second schedule, a control unit registered in the second calendar system is provided. The control unit provides a template to be used in the shared schedule.

The calendar linkage method according to the second feature is a method of linking a first calendar system that manages the first schedule and a second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule. .. The calendar cooperation method includes a step of specifying the first schedule to be managed by the second calendar system as a shared schedule from the first schedule based on the attribute information of the first schedule, and the shared schedule. Is included in the second calendar system as the second schedule, and a step of providing a template used in the shared schedule.

According to the present invention, it is possible to provide a calendar cooperation system and a calendar cooperation method that can support the appropriate implementation of a schedule.

FIG. 1 is a diagram showing a calendar cooperation system 100 according to an embodiment. FIG. 2 is a diagram showing a first server 50 according to an embodiment. FIG. 3 is a diagram showing a second server 70 according to the embodiment. FIG. 4 is a diagram showing a first calendar system according to the embodiment. FIG. 5 is a diagram showing a second calendar system according to the embodiment. FIG. 6 is a diagram for explaining a method of specifying the shared schedule according to the embodiment. FIG. 7 is a diagram showing a calendar cooperation method according to the embodiment. FIG. 8 is a diagram showing a calendar cooperation method according to the embodiment. FIG. 9 is a diagram showing a calendar cooperation system 100 according to the first modification. FIG. 10 is a diagram showing a calendar cooperation method according to the second modification.

Hereinafter, embodiments will be described with reference to the drawings. In the description of the drawings below, the same or similar parts are designated by the same or similar reference numerals.

However, it should be noted that the drawings are schematic and the ratio of each dimension may differ from the actual one. Therefore, the specific dimensions should be determined in consideration of the following explanation. In addition, it goes without saying that there may be parts in which the relations or ratios of the dimensions of the drawings are different from each other.

[Summary of disclosure]
The calendar cooperation system according to the outline of the disclosure links the first calendar system that manages the first schedule and the second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule. The calendar cooperation system specifies the first schedule to be managed by the second calendar system as a shared schedule from the first schedule based on the attribute information of the first schedule, and sets the shared schedule as the second schedule. It is equipped with a control unit to be registered in the calendar system. The control unit provides a template to be used in the shared schedule.

The calendar cooperation method according to the outline of the disclosure links the first calendar system that manages the first schedule and the second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule. The calendar cooperation method includes a step of specifying the first schedule to be managed by the second calendar system as a shared schedule from the first schedule based on the attribute information of the first schedule, and the shared schedule. Is included in the second calendar system as the second schedule, and a step of providing a template used in the shared schedule.

In the outline of the disclosure, from the first schedule, the first schedule to be managed by the second calendar system is specified as a shared schedule based on the attribute information of the first schedule. Further, the calendar cooperation system is provided with a template used in the shared schedule. According to such a configuration, since the first schedule managed by the first calendar system is appropriately registered in the second calendar system as a shared schedule, the implementation history of the shared schedule can be appropriately managed. Furthermore, since the template used in the shared schedule is provided, not only the parties but also a third party can grasp the implementation history of the shared schedule.

In the outline of the disclosure, the first calendar system is a system in which each member belonging to the organization registers an individual schedule (first schedule). Although not particularly limited, as the first calendar system, an existing system that manages the first schedule can be used mainly for the purpose of managing the schedule of the future schedule.

In the outline of the disclosure, the second calendar system is a system that manages the second schedule for the purpose of managing the execution history of the schedule. The second schedule may be viewed by a third party (eg, an organization's personnel personnel) or the like.

Although not particularly limited, the case where the second schedule is the interview schedule will be illustrated below. The interview may include an interview (regular) or an interview (management by objectives). The interview (regular) may be conducted in a relatively longer cycle than the interview (management by objectives), or may be conducted in a relatively shorter cycle than the interview (management by objectives). The interview (regular) may be a one-to-one interview conducted between the member and the member's direct supervisor, or a one-to-many interview conducted between the member and two or more superiors of the member. You may. The interview (management by objectives) may be a one-to-many interview conducted between the member and two or more bosses of the member, or a one-to-one interview conducted between the member and the boss who reports directly to the member. There may be.

[Embodiment]
(Calendar cooperation system)
The calendar cooperation system according to the embodiment will be described below. FIG. 1 is a diagram showing a calendar cooperation system 100 according to an embodiment.

As shown in FIG. 1, the calendar cooperation system 100 includes a first terminal 10, a second terminal 20, a first server 50, and a second server 70. The first terminal 10, the second terminal 20, the first server 50, and the second server 70 are connected by the network 200. Although not particularly limited, the network 200 may be configured by an Internet network. The network 200 may include a local area network, a mobile communication network, or a VPN (Virtual Private Network).

The first terminal 10 is a terminal for inputting a first schedule managed by the first calendar system. For example, the first terminal 10 may be a personal computer, a smartphone, or a tablet terminal. In FIG. 1, two or more first terminals 10 used by two or more subjects are illustrated.

The second terminal 20 is a terminal for viewing the second schedule managed by the second calendar system. For example, the second terminal 20 may be a personal computer, a smartphone, or a tablet terminal. FIG. 1 illustrates one second terminal 20 used by one person in charge of personnel.

The first server 50 is a server that provides the first calendar system. Specifically, the first server 50 stores (manages) the first schedule. The first calendar system is a system in which each member belonging to the organization registers an individual schedule (first schedule). As the first calendar system, an existing system for managing the first schedule can be used mainly for the purpose of managing the schedule of the future schedule. Details of the first server 50 will be described later (see FIG. 2).

The second server 70 is a server that provides a second calendar system. Specifically, the second server 70 stores (manages) the second schedule. The second calendar system is a system that manages the second schedule for the purpose of managing the execution history of the schedule. As the second calendar system, a new system introduced for the purpose of managing the interview implementation history can be used. Details of the second server 70 will be described later (see FIG. 3).

Here, the first server 50 may be realized by SaaS (Service as a Software). Similarly, the second server 70 may be realized by SaaS. The first server 50 may be a server that can cooperate with the second server 70. The second server 70 may be constructed by an organization to which the members related to the second schedule registered in the second server 70 belong, or may be constructed by a third party different from the organization.

(1st server)
Hereinafter, the first server according to the embodiment will be described. FIG. 2 is a diagram showing a first server 50 according to an embodiment. As shown in FIG. 2, the first server 50 includes a communication unit 51, a first DB (Database) 52, and a control unit 53.

The communication unit 51 is composed of a communication module. The communication module may be a wireless communication module that conforms to standards such as IEEE802.11a / b / g / n, ZigBee, Wi-SUN, LTE, and 5G, and a wired communication module that conforms to standards such as IEEE802.3. It may be. For example, the communication unit 51 receives the first schedule from the first terminal 10.

The first DB 52 is composed of a storage medium such as a non-volatile memory, an HDD (Hard Disk Drive), and a magnetic tape. For example, the first DB 52 stores (manages) the first schedule registered by the first terminal 10.

The control unit 53 may include at least one processor. At least one processor may be composed of a single integrated circuit or may be composed of a plurality of communicably connected circuits (such as integrated circuits and / or discrete circuits). For example, the control unit 53 controls each component of the first server 50.

(Second server)
Hereinafter, the second server according to the embodiment will be described. FIG. 3 is a diagram showing a second server 70 according to the embodiment. As shown in FIG. 3, the second server 70 includes a communication unit 71, a second DB (Database) 72, and a control unit 73.

The communication unit 71 is composed of a communication module. The communication module may be a wireless communication module that conforms to standards such as IEEE802.11a / b / g / n, ZigBee, Wi-SUN, LTE, and 5G, and a wired communication module that conforms to standards such as IEEE802.3. It may be. For example, the communication unit 71 receives the attribute information of the first schedule from the first server 50. The communication unit 71 may receive the second schedule from the first terminal 10.

The second DB 72 is composed of a storage medium such as a non-volatile memory, an HDD (Hard Disk Drive), and a magnetic tape. For example, the second DB 72 stores (manages) the second schedule. The second schedule may include a shared schedule acquired in cooperation with the first server 50. The second schedule may include a second schedule registered by the first terminal 10.

The control unit 73 may include at least one processor. At least one processor may be composed of a single integrated circuit or may be composed of a plurality of communicably connected circuits (such as integrated circuits and / or discrete circuits). For example, the control unit 73 controls each component of the second server 70.

In the embodiment, the control unit 73 specifies the first schedule to be managed by the second calendar system as a shared schedule based on the attribute information of the first schedule, and registers the shared schedule as the second schedule in the second calendar system. do. The control unit 73 provides a template to be used in the shared schedule.

Further, the control unit 73 may manage the execution history of the shared schedule based on the input result for the template. The implementation history may include a history of whether or not an interview with a member has been conducted. The implementation history may include the progress of the interview with a member. The implementation history may include the progress of the interview with respect to an organization (eg, the number or percentage of members who have completed the interview).

(1st calendar system)
Hereinafter, the first calendar system according to the embodiment will be described. FIG. 4 is a diagram showing a first calendar system according to the embodiment.

As described above, the first calendar system is a system in which each member belonging to the organization registers an individual schedule (first schedule). Therefore, as shown in FIG. 4, the first schedule is managed for each member.

Coordination of the two first calendar systems may be allowed. Specifically, in the first calendar system of one member, the first schedule permitted by another member may be registered.

Here, the first schedule includes various attribute information. For example, the attribute information is registered in the first calendar system using the first terminal 10.

Although not particularly limited, the attribute information may include information elements such as title, time, participants, place, and description. The title is an item that can be arbitrarily input by the member, and is an information element representing the outline of the first schedule. The time is an item that can be arbitrarily input by the member, and is an information element representing the date and time when the first schedule is scheduled. The time may be specified by a combination of a start date, an end date, a start time, an end time, and the like. A participant is an item that can be arbitrarily input by a member, and is an information element representing a participant who participates in the first schedule. Participants may be identified by name or by email address. The place is an item that can be arbitrarily input by the member, and is an information element representing the place where the first schedule is scheduled. The description is an item that can be arbitrarily input by the member, and is an information element representing the details of the first schedule.

In the embodiment, since the first calendar system does not have the purpose of managing the execution history of the interview, a specific input method may not be defined as the input method of the attribute information. The specific input method is a method such as selecting a predetermined item by a pull-down method.

(2nd calendar system)
The second calendar system according to the embodiment will be described below. FIG. 5 is a diagram showing a second calendar system according to the embodiment.

As described above, the second calendar system is a system that manages the second schedule for the purpose of managing the execution history of the schedule. Therefore, as shown in FIG. 5, the second schedule is not managed for each member, but for each organization to which the member belongs.

The second calendar system may set the viewing authority of the second schedule. Specifically, one member may not have the viewing authority of the second schedule not related to himself / herself, but may have the viewing authority of the second schedule related to himself / herself. Personnel personnel may have permission to view all second schedules.

Here, the second schedule includes various attribute information. For example, the attribute information may be registered based on the attribute information of the first schedule. The attribute information may be registered in the second calendar system using the first terminal 10.

Although not particularly limited, the attribute information may include information elements such as title, time, participants, place, and description. Since these information elements are the same as the attribute information of the first schedule described above, the description thereof will be omitted except for differences.

In the second embodiment, since the second calendar system has the purpose of managing the execution history of the interview, a specific input method is defined as the input method of the attribute information. The specific input method is a method such as selecting a predetermined item by a pull-down method.

For example, with respect to the title, items that can be input (registered) as the title may be predetermined for the purpose of totaling the implementation history. For example, the title may be of two types, an interview (regular) and an interview (goal management). Similarly, participants may be limited to members belonging to the organization. Members belonging to an organization may be identified by the email address used by the organization.

(How to specify the shared schedule)
Hereinafter, a method for specifying the shared schedule according to the embodiment will be described. FIG. 6 is a diagram for explaining a method of specifying the shared schedule according to the embodiment. Here, a case where the shared schedule to be registered as the second schedule is a predetermined type of interview will be described. There are two types of interviews: interviews (regular) and interviews (management by objectives).

As shown in FIG. 6, the shared schedule registered as the second schedule in the second calendar system is associated with the attribute information of the first schedule. Such a correspondence may be predetermined or may be constructed by machine learning including AI (Artificial Intelligence).

Under such a premise, the second server 70 (control unit 73) may specify the first schedule including the predetermined specific attribute information as the shared schedule. The specific attribute information includes one or more information elements selected from the title, place, time, description and participants of the first schedule.

For example, the second server 70 may determine that the first schedule is related to an interview (regular) when the title or description of the first schedule includes keywords such as regular, monthly, and interview. That is, the second server 70 specifies such a first schedule as a shared schedule. When the shared schedule is registered as the second schedule, the second server 70 may change the title of the second schedule (shared schedule) to a predetermined interview (regular). The above-mentioned keywords may be registered in the second server 70 (for example, the control unit 73). For example, a keyword arbitrarily selected by the user may be registered in the second server 70 (for example, the control unit 73).

On the other hand, when the title or explanation of the first schedule includes keywords such as goal setting, goal management, beginning of period, and interview, the second server 70 states that the first schedule is related to interview (goal management). You may judge. That is, the second server 70 specifies such a first schedule as a shared schedule. When the shared schedule is registered as the second schedule, the second server 70 may change the title of the second schedule (shared schedule) to a predetermined interview (management by objectives).

Here, an example is illustrated in which it is determined whether or not the first schedule is a shared schedule based on the keywords included in the title or description of the first schedule. However, whether or not the first schedule is a shared schedule may be determined using other attribute information such as location, time and participants.

Furthermore, as shown in FIG. 6, the shared schedule is associated with the template. For example, an interview (regular) is associated with a first template, and an interview (management by objectives) is associated with a second template. The format of the template such as the first template and the second template is arbitrary. The template contains at least the required input items used to determine if the interview was conducted. The template may include arbitrary input items that are not used to determine whether the interview has been conducted. The first template may include the same input items as the second template, or may include input items different from the second template.

For example, when the first template is associated with the interview (regular) conducted for each quarter, the first template includes items for inputting a review of the previous quarter, an action (plan) of the next quarter, and the like. But it may be. When the second template is associated with the monthly interview (goal management), the second template may include items for inputting the progress status for the goal, the action for achieving the goal, and the like. good.

Under such a premise, the second server 70 (control unit 73) manages the execution history of the shared schedule based on the input result for the template. History may be included. For example, the second server 70 may determine that the interview has been conducted when there are input results for all the required input items. The implementation history may include the progress of the interview with a member. For example, the second server 70 may determine the progress of the interview based on the ratio of the input items for which the input results exist to all the essential input items. The implementation history may include the progress of the interview with respect to an organization (eg, the number or percentage of members who have completed the interview).

(Calendar cooperation method)
The calendar cooperation method according to the embodiment will be described below. 7 and 8 are diagrams showing a calendar cooperation method according to the embodiment.

First, the registration of the shared schedule will be described with reference to FIG. 7. Here, a case of registering the first schedule in the future will be described.

As shown in FIG. 7, in step S10, the first terminal 10 transmits the first schedule to the first server 50. The first schedule includes arbitrary attribute information.

In step S11, the first server 50 registers the first schedule.

In step S12, the second server 70 sends a message requesting the attribute information of the first schedule to the first server 50.

In step S13, the first server 50 transmits the attribute information of the first schedule to the second server 70.

In step S14, the second server 70 specifies the first schedule to be registered in the second calendar system as the shared schedule based on the attribute information of the first schedule. The second server 70 registers the shared schedule as the second schedule.

Here, the processes of steps S12 to S14 may be executed periodically. When the registration of the first schedule can be notified from the first calendar system to the second calendar system, the processes of steps S12 to S14 may be executed according to the registration of the first schedule.

Secondly, the provision of the template will be described with reference to FIG. Here, a case where the second schedule is implemented will be described.

As shown in FIG. 8, in step S20, the first terminal 10 transmits a message requesting a template to the second server 70.

In step S21, the second server 70 transmits the template to the first terminal 10.

In step S22, input to the template is executed. The input of the template may be reflected in the second server 70 when the upload operation of the first terminal 10 is executed, or may be reflected in the second server 70 in real time by the input operation of the first terminal 10. ..

In step S23, the second server 70 manages the execution history of the interview. The interview execution history is managed by the input result for the template.

In step S24, the second terminal 20 transmits a message requesting the execution history of the interview to the second server 70.

In step S25, the second server 70 transmits the interview execution history to the second terminal 20.

Here, the execution history may include the input result of the template. The implementation history may include whether or not an interview with a member has been conducted, the progress of the interview with a member, and the progress of the interview with an organization.

(Action and effect)
In the embodiment, the calendar cooperation system 100 specifies the first schedule to be managed by the second calendar system as a shared schedule from the first schedule based on the attribute information of the first schedule. Further, the calendar cooperation system 100 provides a template to be used in the shared schedule. According to such a configuration, since the first schedule managed by the first calendar system is appropriately registered in the second calendar system as a shared schedule, the implementation history of the shared schedule can be appropriately managed. Furthermore, since the template used in the shared schedule is provided, not only the parties but also a third party can grasp the implementation history of the shared schedule.

Here, considering the case where the first calendar system is an existing system that is used daily by members, it is only necessary to register the first schedule in the first calendar system without modifying the first calendar system. , The shared schedule corresponding to the first schedule is registered in the second calendar system as the second schedule. Therefore, duplicate registration for both the first calendar system and the second calendar system can be suppressed, and the convenience of the members is improved.

[Change example 1]
Hereinafter, modification 1 of the embodiment will be described. In the following, the differences from the embodiments will be mainly described.

In modification 1, the calendar linkage system 100 has a personnel server 90 that stores the correlation of members belonging to the organization, as shown in FIG. The personnel server 90 has a personnel DB (Database). The personnel DB stores information such as organization email address, member number, name, personnel transfer history, employment condition history, hire date, date of birth, gender, and organization information.

The organization email address is the email address assigned to the member. The organization email address may be used in the distribution of the questionnaire. The member number is a number assigned to a member. The name is the name of the member. The member number and name may be used to identify the target person who answers the question. The personnel transfer history may include the history of the department to which the member belongs, the history of the member's job title, and the like. The employment condition history may include a history of the member's occupation, a history of grades, a history of employment form, and the like. The date of joining the company is the date when the member joined the organization. The date of birth is the date of birth of the member. Gender is the gender of the member. The organization information may include the name of the organization, the number of members of the organization, and the like. Personnel transfer history, employment condition history, hire date, date of birth, gender, and organizational information may be considered as attributes used in the analysis of answers to questions.

Under such a premise, the second server 70 (control unit 73) specifies the first schedule to be managed by the second calendar system as a shared schedule based on the correlation of the participants. For example, the second server 70 determines that the first schedule is an interview (regular) when the participants of the first schedule are a member and a boss who reports directly to the member, and shares the first schedule. Specify as a schedule. On the other hand, the second server 70 determines that the first schedule is an interview (management by objectives) when the participants of the first schedule are three or more members and two or more bosses of the members, and the second server 70 is the first. 1 Specify the schedule as a shared schedule.

The second server 70 may specify the first schedule to be managed by the second calendar system as a shared schedule based on attribute information other than the participants, for example, a key third included in the title or description.

(Action and effect)
In the first modification, the calendar cooperation system 100 specifies the first schedule to be managed by the second calendar system as a shared schedule based on the correlation of the participants. With such a configuration, the accuracy of specifying the shared schedule is improved.

[Change example 2]
Hereinafter, modification 2 of the embodiment will be described. In the following, the differences from the embodiments will be mainly described.

In the second modification, it is assumed that the first schedule is erroneously specified as a shared schedule. When the shared schedule deletion operation is executed, the second server 70 (control unit 73) does not delete the first schedule corresponding to the shared schedule from the first calendar system, but the second schedule corresponding to the shared schedule. From the second calendar system.

Here, the deletion operation may be an operation using a terminal having a specific authority. For example, the second server 70 may not accept the deletion operation using the first terminal 10, but may accept the deletion operation using the second terminal 20. According to such a configuration, it is possible to suppress an illegal deletion operation by the first terminal 10.

(Calendar cooperation method)
The calendar cooperation method according to the second modification will be described below. FIG. 10 is a diagram showing a calendar cooperation method according to the embodiment. Here, a case where the deletion operation using the first terminal 10 is not accepted and the deletion operation using the second terminal 20 is accepted will be illustrated.

As shown in FIG. 10, in step S30, the second server 70 receives a message requesting deletion of the shared schedule from the first terminal 10 in response to the deletion operation using the first terminal 10.

In step S31, the second server 70 transmits a message refusing to delete the shared schedule to the first terminal 10.

In step S32, the second server 70 receives a message requesting deletion of the shared schedule from the second terminal 20 in response to the deletion operation using the second terminal 20.

In step S33, the second server 70 sends a message permitting the deletion of the shared schedule to the second terminal 20.

In step S34, the second server 70 does not delete the first schedule corresponding to the shared schedule from the first calendar system, but deletes the second schedule corresponding to the shared schedule from the second calendar system.

For convenience of explanation, FIG. 10 merely illustrates a case in which the processes of steps S32 to S34 are executed after the processes of steps S30 to S31. The processes of steps S32 to S34 are independent of the processes of steps S30 to S31. Therefore, the processes of steps S30 to S31 do not have to be executed.

(Action and effect)
In the second modification, the calendar linkage system 100 does not delete the first schedule corresponding to the shared schedule from the first calendar system when the operation to delete the shared schedule is executed, but the second schedule corresponding to the shared schedule. From the second calendar system. According to such a configuration, an appropriate shared schedule can be managed as the second schedule even if the specific accuracy of the shared schedule is low.

Furthermore, in cases where the shared schedule is specified by machine learning including AI, appropriate learning can be executed. For example, consider a case where a learning model that specifies the first schedule to be specified as a shared schedule is used by inputting the attribute information of the first schedule. In such a case, the accuracy of the learning model is improved by reducing the weighting of the attribute information used as a specific judgment material of the deleted shared schedule. In addition, the accuracy of the learning model is improved by increasing the weighting of the attribute information used as a specific judgment material of the shared schedule that has not been deleted.

[Change example 3]
Hereinafter, modification 3 of the embodiment will be described. In the following, the differences from the embodiments will be mainly described.

In the third modification, a case where a first calendar system exists for each member, that is, a case where two or more calendar systems are provided as the first calendar system will be described. In such a case, the second server 70 (control unit 73) includes the common attribute information when the attribute information of the first schedule registered in each of the two or more calendar systems includes the common attribute information. The schedule may be specified as a shared schedule.

For example, when the time and place of the first schedule of the member is the same as the time and place of the first schedule of the boss who reports to the member, the second server 70 (control unit 73) interviews these first schedules. The first schedule may be specified as a shared schedule by determining that it is (regular). On the other hand, when the time and place of the first schedule of the member is the same as the time and place of the first schedule of two or more bosses of the member, the second server 70 (control unit 73) uses these first schedules. May be determined to be an interview (management by objectives) and the first schedule may be specified as a shared schedule. In these cases, time and place are common attribute information.

The second server 70 may specify the first schedule to be managed by the second calendar system as a shared schedule based on attribute information other than time and place, for example, a key third included in the title or description.

(Action and effect)
In the third modification, the calendar linkage system 100 specifies the first schedule including the common attribute information as a shared schedule when the attribute information of the first schedule registered in each of the two or more calendar systems includes the common attribute information. do. According to such a configuration, for example, even if the first schedule does not include the participants, the accuracy of specifying the shared schedule is improved.

[Other Embodiments]
Although the present invention has been described by embodiments described above, the statements and drawings that form part of this disclosure should not be understood to limit the invention. Various alternative embodiments, examples and operational techniques will be apparent to those skilled in the art from this disclosure.

In the embodiment, the case where the identification of the shared schedule is executed by the second server 70 has been illustrated. However, the embodiment is not limited to this. For example, if the function of specifying the shared schedule can be implemented in the first calendar system, the specification of the shared schedule may be executed by the first server 50. Alternatively, the specification of the shared schedule may be executed by a server other than the first server 50 and the second server 70.

In the embodiment, two types of interviews, an interview (regular) and an interview (management by objectives), are exemplified. However, the embodiment is not limited to this. For example, interviews for each department may be managed as different types of interviews, and interviews for each position may be managed as different types of interviews. In such a case, the above-mentioned template may be defined for each type of interview.

In the embodiment, the case where the second schedule managed by the second calendar system, that is, the second schedule managed for the purpose of managing the implementation history is an interview is illustrated. However, the embodiment is not limited to this. The second schedule may be a meeting or a customer visit.

Although not specifically mentioned in the embodiment, the organization may be an organization having legal personality or an organization not having legal personality. The organization may be a base or department that constitutes these organizations.

10 ... 1st terminal, 20 ... 2nd terminal, 50 ... 1st server, 51 ... communication unit, 52 ... 1st DB, 53 ... control unit, 70 ... 2nd server, 71 ... communication unit, 72 ... 2nd DB, 73 ... control unit, 100 ... calendar cooperation system, 200 ... network

Claims (7)

It is a calendar cooperation system that links the first calendar system that manages the first schedule and the second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule.
From the first schedule, the first schedule to be managed by the second calendar system is specified as a shared schedule based on the attribute information of the first schedule, and the shared schedule is designated as the second schedule. 2 Equipped with a control unit to be registered in the calendar system
As the execution history of the shared schedule, the control unit has at least a history of whether or not the shared schedule has been implemented, a degree of progress of the shared schedule for members belonging to the organization, and a degree of progress of the shared schedule for the organization. to manage any one,
The control unit specifies the first schedule to be managed by the second calendar system as the shared schedule based on the correlation of the participants of the first schedule, which is one of the predetermined specific attribute information. to, calendar cooperation system. It is a calendar cooperation system that links the first calendar system that manages the first schedule and the second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule.
From the first schedule, the first schedule to be managed by the second calendar system is specified as a shared schedule based on the attribute information of the first schedule, and the shared schedule is designated as the second schedule. 2 Equipped with a control unit to be registered in the calendar system
As the execution history of the shared schedule, the control unit has at least a history of whether or not the shared schedule has been implemented, a degree of progress of the shared schedule for members belonging to the organization, and a degree of progress of the shared schedule for the organization. Manage any one and
When two or more calendar systems are provided as the first calendar system, the control unit receives common attribute information when the attribute information of the first schedule registered in each of the two or more calendar systems includes common attribute information. A calendar linkage system that specifies the first schedule including the common attribute information as the shared schedule. The control unit provides a template to be used in the shared schedule.
The calendar linkage system according to claim 1 or 2 , wherein the control unit manages the execution history of the shared schedule based on the input result for the template. The control unit specifies the first schedule including the specific attribute information as the shared schedule.
The calendar according to claim 1 , wherein the specific attribute information includes one or more information elements selected from the title, place, time and description of the first schedule in addition to the participants of the first schedule. Cooperation system. When the deletion operation of the shared schedule is executed, the control unit does not delete the first schedule corresponding to the shared schedule from the first calendar system, but the second schedule corresponding to the shared schedule. The calendar cooperation system according to any one of claims 1 to 4 , wherein is deleted from the second calendar system. It is a calendar linkage method of a calendar linkage system that links the first calendar system that manages the first schedule and the second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule.
Step A in which the calendar cooperation system specifies the first schedule to be managed by the second calendar system as a shared schedule from the first schedule based on the attribute information of the first schedule.
Step B, in which the calendar cooperation system registers the shared schedule as the second schedule in the second calendar system,
As the implementation history of the shared schedule, the calendar cooperation system includes a history of whether or not the shared schedule has been implemented, a degree of progress of the shared schedule for members belonging to the organization, and a degree of progress of the shared schedule for the organization. With step C to manage at least one of them ,
In the step A, the first schedule including the predetermined specific attribute information is specified as the shared schedule, and based on the correlation of the participants of the first schedule, which is one of the specific attribute information. A calendar linkage method including a step of specifying the first schedule to be managed by the second calendar system as the shared schedule. It is a calendar linkage method of a calendar linkage system that links the first calendar system that manages the first schedule and the second calendar system that manages the second schedule for the purpose of managing the execution history of the schedule.
Step A in which the calendar cooperation system specifies the first schedule to be managed by the second calendar system as a shared schedule from the first schedule based on the attribute information of the first schedule.
Step B, in which the calendar cooperation system registers the shared schedule as the second schedule in the second calendar system,
As the implementation history of the shared schedule, the calendar cooperation system includes a history of whether or not the shared schedule has been implemented, a degree of progress of the shared schedule for members belonging to the organization, and a degree of progress of the shared schedule for the organization. With step C to manage at least one of them,
In step A, when two or more calendar systems are provided as the first calendar system, and the attribute information of the first schedule registered in each of the two or more calendar systems includes common attribute information. A calendar linkage method for specifying the first schedule including the common attribute information as the shared schedule.

Images