JPH03130870A - Schedule display device - Google Patents

Abstract

PURPOSE:To reduce the cost required for individual updating of an individual schedule and to prevent the loss of integration of data that is caused by the individual updating by controlling collectively the schedule information common to plural users. CONSTITUTION:The group schedule storage parts 311 - 313 and 321 - 323 are provided to store the group schedules related to plural users together with a member storage part 353 which stores the relative members related to the group schedules, and a priority storage part 352 which stores the priority ranks of the group and individual schedules. Thus each user is not required to input the schedules related to plural users into an individual schedule.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of Industrial Application The present invention relates to a schedule display device for storing and displaying schedules.

[Conventional technology] An example of the configuration of a conventional schedule system is shown in FIG.

When the user inputs the date, time, and items of the schedule from the human resource section 140, the information is sent to the personal schedule storage section 160 according to instructions from the control section 100. The personal schedule storage unit 160 stores the date of the item in the date storage unit 161 and the time of the item in the time storage unit 16 according to instructions from the control unit 100.
2, the items are stored in the personal schedule content storage section 163. When the user tries to read out the schedule for the current day from the input unit 140, time information is read out from the timer unit 105 according to an instruction from the control unit 100, and is sent to the selection unit 130 via the control unit 100 as the date information of the current day. sent to. When the selection unit 130 receives the date information according to the instruction from the control unit 100, the selection unit 130 stores the date information in the personal schedule storage unit 160.
The schedule contents and time corresponding to the date and time are read out and transmitted to the display unit 150 according to instructions from the control unit 100. The display unit 150 displays the received schedule information according to instructions from the control unit 100, dividing it into year, month, day, time, and content. In addition, if the date information is not specified,
In response to an instruction from the control section 100, timer information is transmitted from the timer section 105 to the selection section 130. In response to instructions from the control unit 100, the selection unit 130 reads out the schedule contents and time applicable to the current day based on the received timer information, and
The information is transmitted to the display unit 150 and displayed according to instructions from the control unit 100.

When the user manually enters the date and time for which the schedule is to be confirmed from the human resource section 140, the human resource section 140 transmits the date and time information to the selection section 130 according to instructions from the control section 100. Selection section 13
0 reads out the schedule contents and time of the corresponding date and time from the personal schedule information storage section 160 using manually inputted information according to instructions from the control section 100, and displays them on the display section 150.
Send to. The display unit 150 displays the received schedule information according to instructions from the control unit 100, dividing it into year, month, day, time, and content. 101 is the entire device.

[Problems to be Solved by the Invention] Schedule information is often used for holding meetings among multiple users, setting meeting points, and setting deadlines. However, in this case, since it is necessary to uniformly write to a plurality of individual schedules, there is a drawback that setting schedules for N people requires N number of borrowers. In addition, if the schedules are written separately, there are also drawbacks such as inconsistencies in schedule settings. Another disadvantage is that attempting to write to multiple individual schedules at the same time complicates recovery in the event of a failure, and increases costs for exclusive control and recovery processing.

The present invention provides a schedule display device that provides schedule information stored in a plurality of schedule storage units to a user in an integrated manner, thereby eliminating the need for manually inputting information into a plurality of personal schedule storage units. The purpose is to provide

[Means and effects for solving the problem] In order to achieve the above object, the present invention provides a schedule display device having schedule input, schedule display, and schedule storage functions, which stores group schedules related to a plurality of users. It is equipped with a group schedule storage unit, a member storage unit that stores related members related to the group schedule, and a priority storage unit that stores the priorities of group schedules and individual schedules, and includes a group schedule storage unit that stores related members related to the group schedule. Each user does not have to manually create their own schedule. In addition, by manually adjusting the priority between the names of related members and multiple schedule storage units, it is possible to create a schedule that is not necessarily prioritized by the organization or group's schedule, but by giving priority to the individual schedule in the case of executives. Priority settings can be made flexibly.

C Example] FIG. 1 shows an embodiment of the present invention.

First, the operation according to claim 1 will be explained. This will be explained with reference to the initial setting flowchart shown in FIG.

To operate the apparatus of the present invention, first, a schedule storage unit corresponding to an individual is assigned and an individual is registered.

This schedule storage unit is a personal schedule storage unit 16.
This is realized as 0. Although there is only one personal schedule storage unit 160 in the diagram of the embodiment, it can be easily inferred that the individual schedule storage unit 160 is allocated by the number of members.

Next, a group schedule storage unit that stores a group schedule is assigned to each schedule related to a plurality of users, and group registration is performed. In FIG. 1, there are two storage units, a group schedule storage unit and a group B schedule storage unit, and it is easily possible to expand this to N units. Since the schedule storage unit can be realized as a table on RAM (Random Access Memory), it can be easily expanded to N, and according to such an implementation method, It is also easily possible to increase the number of group schedules.

Next, the relationship between the individual schedule and the group schedule is registered.

For each group schedule, user identification information related to the group schedule is stored. The user identification information is given by this device or the system operator, and uniquely identifies the user throughout the network. For example, it may be a user number such as 1109, or it may be a user login name such as t-yamakaml that is uniquely set on the network. Any information that can be used to search a table and that is uniquely determined for the user may be used.

A group schedule identifier is stored in the group schedule identifier storage unit 351 of the group schedule related information storage unit 350, and identification information of related group members, such as names and computer names, is stored in the related member storage unit 353 in correspondence with the group schedule identifier. .

A group schedule identifier is assigned by the device to distinguish between multiple group schedules, and if it is possible to identify group schedules and individual schedules, it can also be a number obtained by the registration order such as 1, 2, or 3. Alternatively, it may be a character string such as a group name. It is easily analogous to assign an identifier to a personal schedule in the same way, and to treat the personal schedule as a special case in which there is only one related member among the group schedules.

If the group schedule is not stored on the entire device 301, such as when the group schedule storage units are distributed on the network, in other words, if there is a group schedule on the network, the group schedule network location storage unit 354 is further stored. Network location information for accessing the group schedule is registered and stored. If a group schedule is stored on the entire device 301, that is, if there is no group schedule on the network, "no network location" is stored. This can be stored, for example, by associating 0 with this "no network location".

In this case, if you want to issue a warning instead of prohibiting input, register priority for warning in the schedule. Otherwise, terminate.

In addition, the group schedule priority is set to correspond to the group schedule, and the group schedule priority storage unit 3
52.

For example, the priority of the personal schedule is O, the priority of the section is 10, the priority of the section manager is 18, and the priority of the section is 2.
0, Deputy manager's priority is 26, Manager's priority is 28, Department's priority is 30. The priority of ceremonial occasions within the department is 35, the manager's priority is 38, and the priority of special projects is 40. Headquarters priority is 50, company ceremonial occasion priority is 55, company priority is 60, president's priority is 68, calendar schedule priority is 70, VIP schedule priority is 80.
, and so on.

Alternatively, priorities can be set in a hierarchical manner so that priorities can be defined for items above and below the hierarchy, but priorities cannot be defined for items that have no parent-child relationship. In this case, the priority is set to have this structure. That is, for example, the priority of the 1st Development Department is 1.1, the priority of the 1st Development Department, 1st Development Division is 1.1.1, and the priority of the 1st DFJ Department, 2nd Development Division is 1. .1.2, between the 1st Development Department common schedule and the 1st Development Department to 1 Development Division common schedule, and '! jSl
There is a priority between the development department common schedule and the 1st development department 2nd development division common schedule, and the former takes precedence, but the 1st development department 1st development division common schedule and the 1st development division common schedule
There is no priority relationship between the M Development Department 2nd Development Division common schedules, and they can be set independently. In this case, the priority is a
,b,c.

It is expressed as a string of numbers separated by "," such as d,..., and if one priority contains the other priority, only in that case is it included. It is sufficient to specify that the one with the shorter priority level takes priority. In the previous example, if the priority of the 2nd Development Department is 1.2, this schedule will have priority over the 1st Development Department, the 1st Development Department, 1st Development Section, and the 1st Development Department, 2nd Development Section. Schedules can be set independently without any relationship. For example, if the priority of the development headquarters is 1, this development headquarters common schedule will be
There is a priority relationship with, and priority is given to, the Development Division.

Alternatively, it is also possible to store the priority of each group schedule with respect to other group schedules as an inequality sign.

When such initial settings are completed, each user performs manual operation from the human power section 140 on the corresponding group schedule or individual schedule.

After accepting the schedule input, the human power unit 140 stores the input in the expanded schedule storage unit 310 for each schedule according to instructions from the control unit 300. for example,
If the personal schedule is created manually, it is stored in the personal schedule storage section 160. When a group schedule is input, the date is stored in the group A schedule date storage section 311, the time is stored in the group schedule content storage section 312, and the content is stored in the group schedule content storage section 313.

Similarly, when a group schedule is input, the date is stored in the group schedule content storage section 321, the time is stored in the group schedule content storage section 322, and the content is stored in the group schedule content storage section 323.

The same applies even if many other group schedules are defined and storage units are allocated.

When the user refers to the schedule, he or she manually enters a reference command and reference date and time from the input unit 140. When the human power section 140 accepts the human power according to the instruction from the control section 300, it transmits it to the related schedule selection section 330. After receiving the information, the related schedule selection unit 330 reads the personal schedule information from the user's personal schedule 160 and selects the one that corresponds to the date and time. At the same time, the related member information is read from the group schedule related member storage section 353, and all group schedule identification information of which the user who manually made the schedule request is a member is read out and stored in the internal work area of the related schedule selection section 330. Remember. Next, all related group schedule identification + III information are read out in order, the corresponding group schedule contents are read out from the group schedule contents storage section, and the one corresponding to the relevant date and time is selected.

After reading the related schedule information as described above, the related schedule selection unit 330 selects the control unit 300.
According to the instruction, the schedule information of the date and time requested by the user is selected and transmitted to the display section 150. Display section 1
50 displays the received schedule information by dividing it into year, month, day, time, and content according to instructions from the control unit 300.

Further, after reading out the related schedules, the related schedule selection unit 330 reads out the group schedule priority from the group schedule priority storage unit 352, and selects only the most prioritized schedule, or presets a few of the top ones. It is easy to imagine a configuration in which only the specified number of schedules are selected and sent to the display unit 150.

When referring to not only the schedule of the user who requested reading but also the schedule of another person, the above procedure can be easily realized by inputting the identification information of the person to be read from the human power section 140.

The operation according to claim 2 will be explained.

In the operation set forth in claim 1, when all related group schedule identification information is read out in order, the corresponding group schedule contents are read out from the group schedule contents storage section, and the one corresponding to the relevant date and time is selected, The group schedule to be read reads the group schedule network location information from the group schedule network location information storage unit 354, and
Group schedule identification information and group network location information are sent to the interface unit 410 for those that are not set to "No network location", that is, for those whose group schedules are stored in another schedule display device connected via a network. and request a reading. When the interface unit 410 receives the group schedule identification information and the group schedule network location information, the interface unit 410 transmits a read request to the schedule display device Z connected to the network and pointed to by the network location information according to the instruction from the control unit 300. do. Here, the schedule display device Z is another schedule display device as described in the embodiment of the invention that stores the group schedule.

When the schedule display device Z that stores the group schedule connected via the network receives the read request at the interface unit 410, it reads the group schedule storage unit (for example, if it is group A, the schedule display device Z stores the group schedule The requested group schedule information is read out from the date storage section 311, group schedule time storage section 312, and group A schedule content storage section 313) and sent back via the interface section 410.

It can be easily inferred that in this network access, the amount of data transferred can be reduced by transmitting not only the group schedule identification information but also the date and time requested to be displayed via the interface section 410.

On the side that sent the read request, the schedule display device Z
When the information returned from the scheduler is received via the interface section 410, it is transmitted to the related schedule selection section 330 according to instructions from the control section 300, and selection is made manually based on the date and time.

The operation after the related schedule selection unit 330 reads out the selection as described above is that after reading out the related schedule information, the user selects the date and time schedule information requested by the user according to instructions from the control unit 300. and transmits it to the display section 150. The display section 150 displays the received schedule information according to instructions from the control section 300, dividing it into year, month, day, time, and content.

The operation according to claim 3 will be explained.

After the initial settings described in the first aspect of the present invention are completed, each user manually performs manual adjustment on the corresponding group schedule or individual schedule using the manual processing unit 140.

When the manual input for the schedule is accepted, the input unit 140 stores the manual input for each schedule in the expanded schedule storage unit 310 according to instructions from the control unit 300. for example,
When the personal schedule is updated, it is stored in the personal schedule storage section 160. When a group schedule is input, the date is stored in the group A schedule date storage section 311, the time is stored in the group schedule time storage section 312, and the contents are stored in the group A schedule content storage section 313.

Similarly, when the group schedule is manually created, the year, month, and day are stored in the group schedule time storage section 321, the time is stored in the group schedule time storage section 322, and the contents are stored in the group schedule time storage section 323.

The same applies even if many other group schedules are defined and storage units are allocated.

In writing, the protection unit 390 writes the group schedule related member storage unit 3 according to the instruction from the control unit 300.
51, the group schedule priority is read from the group schedule priority storage unit 352, and if a schedule has already been set in the related group schedule, the control unit sends a signal to reject the input. 300 to prevent the schedule from being written to the storage section, and read out and transmit a warning to the display section 150 and the schedule information of the existing high priority group schedule from the schedule content storage section 313. The display unit 150 displays a warning to the user who attempts to perform the manual operation according to instructions from the control unit 300 and the contents of the group schedule that has already been set.

For example, if Mr. X belongs to Group A and the priority of Group A is higher than Mr.
August 7th according to the Group A schedule.
If Mr. detects this duplication and outputs the warning and the duplication information of the group A schedule to the display section 150.

For example, if the manager's schedule has a higher priority than the department's schedule or department's schedule,
Conversely, it is also possible to detect duplication at the time of inputting the schedule of group A schedule (department or section) and to issue a warning.

In addition, when such duplication processing is to be left to the user, it can be easily inferred that the processing of the protection unit 390 is limited to a warning and is set so as not to interfere with the input itself.

FIG. 5 shows a flowchart of the registration procedure. That is, first input the schedule. Check the entries for the next priority group schedule. If there is no conflicting low input schedule, the input is memorized and the process ends. If there is a conflicting low-input schedule and a warning is given priority, the low-input content of the priority schedule is displayed, a warning is given, and the process ends.

If there is a supplementary low input schedule and there is no warning priority, the low input content of the prioritized schedule is displayed, the input is rejected, and the process ends.

FIG. 6 shows a flowchart at the time of display. That is, the personal schedule is displayed first, and if there is no group schedule to prioritize, the process ends. If there is a priority group schedule, but the priority group schedule is not on the network, the low input content of the priority group schedule is displayed and the process ends. If there is a priority group schedule and the priority group schedule is on the network, the registered network location is read. Next, a request is issued to the device located at the read network location to read the corresponding schedule contents, and the schedule contents are read from the network. Then, the low input content of the prioritized group schedule is displayed and the process ends.

Note that this device can be used by connecting a plurality of devices to a network. The network may be something like a local area network or something like wireless transmission. Alternatively, it may be realized on a service built on an application layer such as an electronic bulletin board connected via a telephone network.

Furthermore, it is easily possible to implement the personal schedule storage section of this device by storing it in a portable medium such as an IC card as long as it is readable.

Further, the personal schedule storage section can be configured as a table consisting of a plurality of personal schedule storage sections. The group schedule storage unit can also be configured as one common table containing a plurality of group schedules.

FIG. 2 shows an example in which three devices shown in FIG. 1 are connected to a network such as a LAN. Device 411.412.
413 is a device having the mechanism 301 in FIG. 19
0 is a network such as LAN, and connection line 186
, 187, 188 are connected to the respective devices. In such a network, it is possible to access the schedule information on the above-mentioned network by broadcasting.

It can be easily inferred that the mechanism of this device can also be realized by software.

[Effects of the Invention] As explained above, the schedule display device of the present invention reduces the cost of updating personal schedules individually by collectively managing schedule information common to multiple users, and facilitates data integration. It is possible to prevent schedules from being lost due to individual updates, and to display schedules with high priority by flexible priority setting.

For example, compared to systems that notify schedule changes by e-mail, it is easier to keep schedule data the same throughout the network.

[Brief explanation of the drawing]

FIG. 1 is a configuration explanatory diagram showing one embodiment of the schedule display device of the present invention, FIG. m2 is a configuration explanatory diagram showing an example in which the schedule display device of FIG. FIG. 4 is a flowchart showing an example of initial setting of the schedule display device of the present invention; FIG. 5 is a flowchart showing an example of registration of the schedule display device of the present invention; The figure is a flowchart showing an example of displaying by the schedule display device of the present invention. 100... Control unit, 101... Entire device, 105.
...Timer section, 130... Selection section, 140... Input section, 150... Display section, 160... Personal schedule storage section, 161... Date storage section, 162... Time Storage unit, 163...Personal schedule content storage unit,
300... Control unit, 301... Entire device, 310...
... Expanded schedule storage section, 311... Group schedule priority storage section, 312... Group A schedule special storage section, 313... Group A schedule content storage section, 321... Group schedule priority storage section Section, 322...Group B schedule time storage section, 323...Group B schedule content storage section, 330...Related schedule selection section, 351...
-Group schedule identification information storage unit, 352...
Group schedule priority storage unit, 353...Group schedule related member storage unit, 354...Group schedule network position storage unit, 390...
・Protection section, 410...Interface section, 186...
・Connection line, 187...Connection line, 188...Connection line,
190... LAN, 411... Schedule display device, 412... Schedule display device, 413...
Schedule display device. Figure Figure End Figure Figure

Claims (3)

[Claims] (1) A schedule display device having schedule input, schedule display, and schedule storage functions includes a group schedule storage section that stores group schedules related to multiple users, and a member storage section that stores related members related to the group schedules. A schedule display device comprising: and a priority storage section that stores priorities of group schedules and individual schedules. 2. The schedule display device according to claim 1, further comprising: a network group schedule location storage section that stores the location of the group schedule storage section on the network; and a group schedule inquiry section. 3. The schedule display device according to claim 1, further comprising a group schedule protection unit that rejects schedule input that violates a group schedule based on priority.