JP4166101B2 - Schedule management system, program and recording medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a schedule management system, program, and recording medium that can register, manage, and reference each other's schedules such as individuals and groups on a network in an office, and more particularly, a schedule that exists in a distributed manner. The present invention relates to a schedule management system, a program, and a recording medium that can be referred to centrally.
[0002]
[Prior art]
In recent years, the spread of computer systems has been remarkable, and there has been a remarkable advance in communication technology. In large-scale companies, networks have been established within the same office and between other offices. In this way, information is shared within the company.
[0003]
One example of this is software that manages the schedules of individuals and groups.
In general, when a group meeting is held, it is necessary to check the schedules of itself and other group members to determine a schedule in which the schedule is vacant in common.
In order to perform this work, each member's personal schedule must be made public in the group, and the member inviting the meeting must check the other members' individual schedules one by one.
[0004]
In order to reduce such work, software that provides functions such as managing the group schedule within a group and referring to it among each member to search for a meeting schedule in which each person can participate Is realized.
For example, in the group schedule function in Notes / Domino made by Lotus, if the group name and members belonging to the group are registered, the individual schedule registered for each member can be collected and the group schedule can be displayed as a calendar. .
[0005]
[Problems to be solved by the invention]
The above-described software for managing group schedules manages individuals and group schedules to be managed on a single server computer. However, in this configuration, a large-scale company has a huge amount of data. At the same time, there will be a problem of concentration and increase of load on the server computer.
In order to avoid this situation, large-scale companies are currently managing their schedules separately for each office.
[0006]
However, there are many projects that span offices, and a new problem arises that group schedule management becomes impossible in this case.
[0007]
On the other hand, in general, when managing group schedules, it is impossible to manage without holding information about users. However, in large-scale companies, contracts / changes of employees coming from or leaving employees or from contractors / Since deletion frequently occurs, maintenance of employee information that is a user of the schedule management system becomes a problem.
[0008]
The present invention has been made in consideration of the above-described circumstances, and a schedule for facilitating the maintenance and management of a user master that holds information about users even in a large-scale company where users frequently change. It is an object of the present invention to provide a management system, a program for executing the functions of the schedule management system, and a computer-readable recording medium on which the program is recorded.
[0009]
[Means for Solving the Problems]
In order to solve the above-mentioned problem, claim 1 of the present invention is a schedule management system for managing a schedule of a large number of employees who belong to a plurality of offices and are updated at any time. At least consist of employee number, email address, name, work location and affiliation An employee master DB that holds personnel information, a schedule DB that holds the schedule of employees belonging to each business site, and the location information of the business site and the schedule DB managed by this business site And the server DB table that stores information in correspondence with each employee who is a user of the system, the employee number, e-mail address, name, work location, affiliation, and location information of the schedule DB used by the employee Date User information And a user information creation unit that collectively generates and updates the user master for all employees based on the employee master DB and the server DB table. , User information creation unit The collective generation of the user master in the above generates the user information for all employees, and the update of the user master in the user information creation unit is executed in synchronization with the update of the employee master DB, For an employee that exists but is not in the user master, the user information of the employee is generated. For an employee that exists in both the employee master DB and the user master, the email address of the employee and the employee The user information is updated for the location information of the schedule DB used by the employee, and the retired employee registered in the employee master DB is also updated as a retired employee in the user master. It is characterized by that.
[0011]
Book Claims of the invention 2 In the schedule management system according to claim 1, the user information creation unit is operated as required by an administrator of the system, For an employee that exists in the employee master DB but does not exist in the user master, the user information of the employee is generated, and for an employee that exists in both the employee master DB and the user master, Update the email address and the location information of the schedule DB used by the employee, and update the retired employee registered in the employee master DB as a retired employee in the user master. It is characterized by that.
Claims of the invention 3 In the schedule management system according to claim 1, the employee to be updated is selected and the user information creation unit is operated, For employees who exist in both the employee master DB and the user master, the e-mail address of the employee and the location information of the schedule DB used by the employee are updated, and for retired employees registered in the employee master DB Update as a retired employee in the user master It is characterized by that.
Claims of the invention 4 In the schedule management system according to claim 1, the employee to be updated is selected and the user information creation unit is operated, Based on the personnel information and the server DB table, The user Regenerate the information and change the user master It is characterized by the replacement.
[0012]
Further, the claims of the present invention 5 The computer The , Claims 1 to 4 Of the schedule management system described in any of As each part Machine Ability It is a program to make it.
Further, the claims of the present invention 5 Claims 5 A computer-readable recording medium on which the program of the schedule management system described in 1 is recorded.
[0013]
With the above configuration, even if there are a large number of users who use this system, the employee master updates the user information from the employee master holding the personnel information updated as needed to the user master as needed. Registration / change / deletion of user information in the user master is facilitated when entering or leaving the company or when a contract / change / deletion of a person from a partner company occurs.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, a preferred embodiment according to the schedule management system of the present invention will be described with reference to the drawings. The schedule management system of the present invention (hereinafter also referred to as the present system) is used by a large number of users who belong to offices distributed in a plurality of locations, and is manufactured by Lotus. It is assumed that it is developed based on Notes / Domino.
[0015]
FIG. 1 is a block diagram showing the overall configuration of the schedule management system of the present embodiment. In the figure, the schedule management system has a plurality of offices 10 connected by a network 20.
The office 10 includes a user terminal belonging to the office 10, a database for managing the user's schedule, reservation of common facilities, and the like. The database can be referred to from each office 10 mutually. Yes.
Here, the network 20 is a transmission path for connecting networks laid in each office, and is realized by wire or wireless. For example, a LAN (Local Area Network), WAN by a public line, a dedicated line, etc. (Wide Area Network), the Internet, etc. can be used.
[0016]
The establishment 10 includes an authentication database (DB) 11, a schedule database (DB) 13, a scheduler menu database (DB) 14, a common facility reservation database (DB) 15, an arbitrary number of administrator terminals 16 and an arbitrary number of users. A terminal 17 is connected by a network 18.
[0017]
The authentication DB 11 holds a user ID of a user who uses the system and authority information indicating how far the user can operate, and the user ID (user name or server name, password, Notes license number). , Public key, private key, authentication stamp, etc.) is a database for verifying whether or not there is an authority to use this system.
[0018]
The schedule DB 13 registers a schedule of each user's meeting or business. The schedule DB 13 registers a schedule for each user for one month as one document.
If one schedule is taken as one document in Notes, 20 documents will be created in one month and 240 documents in one year as one schedule per day. If this is used by all employees, the amount of documents will be enormous, and the response time will be slow even if the search is simply displayed.
Therefore, in this system, the document amount is reduced by combining the schedule for one month into one document.
[0019]
As shown in FIG. 2A, the schedule document includes three parts, that is, a header 101, a schedule 102, and high-speed display data 103.
The header 101 includes document number, employee number, schedule date, notes address, name, affiliation, document division index, etc., as information about the user who registered the schedule (see FIG. 2B).
Here, the document number is a sequential number starting from 1, which is assigned when a one-month schedule is divided into a plurality of documents due to a large amount of data.
The document division index is an array in which document numbers of documents having a daily schedule are arranged in order of date.
When the document is divided into a plurality of documents, whether the documents belong to the same schedule is determined by the employee number in the header 101 and the date of the schedule.
[0020]
The schedule 102 is a schedule table in which schedule types, start / end times, business requirements, detailed explanations, and the like are arranged in the number of schedules for each day of the month indicated by “year / month of schedule” in the header 101.
[0021]
When the group schedule “1 week display”, “2 week display” or “1 month display” is performed, the system displays the operating time from the start time to the end time as shown in FIG. As one day, the day is further divided into equal parts (for example, divided into six equal parts) and displayed.
In this display, a figure with colored work status (working place, reservation status and vacation category) for each divided time zone (coloring of the figure is colored with the outline of the figure and the inside of the figure in color) Are displayed separately. For this reason, since it takes time to convert each scheduled time to a figure after obtaining the schedule of all members in the group, when registering the person's schedule, this figure information is created and data for high-speed display It is stored as 103.
[0022]
For example, in the high-speed display data 103, one set of color information indicating the schedule start / end time and the schedule status in that time zone is set as one set, and this is held for each day. As the schedule status and color information, for example, yellow is used during a meeting in the office, orange is used for double booking, green is used when going out, gray is used for working hours, and pink is used for vacation.
[0023]
Note that there is a limit to the capacity that can be registered as one Notes document. For this reason, when the daily schedule is additionally registered, if the data amount of the document for which the schedule is registered exceeds the capacity limit, the next item is written in the generated new document.
(1) Write a header in which the document division index is updated to a new document so as to indicate that the schedule to be added is in the new document.
(2) Write the schedule to be added to a new document.
(3) Write high-speed display data with updated color information for the schedule to be added.
[0024]
The operation functions of the schedule DB 13 include general individual and group schedule registration, update, and deletion. Moreover, the schedule list display and the detailed display at that time can also be performed. The schedule DB 13 has an attribute capable of receiving a mail, and the schedule is registered by a schedule document registration agent that receives the mail and is periodically activated.
[0025]
The scheduler menu DB 14 is a replica database (here, the replica database is a database that is synchronized with each other so as to always have the same contents) and may use this system. A user master that holds information about a certain user and a server DB table that manages information of the database of this system (details will be described later). This user is all employees who work at each office (here, regular employees, contract employees, employees of partner companies, etc. are collectively referred to as employees).
This user master holds the following data for each user.
[0026]
Employee number, notes address, name (notation in kanji, kana and romaji),
Work location, department division, etc.
Location of schedule DB 13 (server name and file name),
Location of common facility reservation DB 15 for each reserved common facility (server name and file name)
[0027]
Furthermore, the group name and information on the constituent members are also registered in the user master by the user or administrator.
[0028]
As the operation function of the scheduler menu DB 14, there is a request from a Web browser operating on the user terminal 17 of the user, batch registration of the user master, batch update at any time, update at any time individual selection, initialization at any time, etc. There is a list of individual and group schedules and common equipment reservations, and detailed information.
[0029]
The common facility reservation DB 15 holds the reservation status of common facilities (conference rooms, meeting corners, personal computers, white boards, projectors, etc.) provided for each business site.
The common equipment reservation document held in the common equipment reservation DB 15 shows the reservation status for one month for each common equipment, the scheduled start / end time, the reservation person and its related persons, etc. for each day of the month. It is only a reservation table.
When reserving the common equipment, exclusive control is performed so that two or more users cannot perform a reservation operation at the same time (details will be described later).
[0030]
The administrator terminal 16 is a terminal used by an administrator of the system provided for each office, and the administrator performs generation / maintenance management of each database of the system.
The administrator terminal 16 is a computer capable of operating a Notes client.
The user terminal 17 is a terminal on which the user of this system performs an operation of a schedule for himself or a group or a reservation for common equipment.
The user terminal 17 is a computer that can operate a Web browser.
The network 18 is a transmission path for connecting each database in the office and between the offices, and the communication protocol between them is TCP / IP.
[0031]
Next, the operation of this system having the above configuration will be described in detail.
(A) Creation and update of user master
4 is a functional configuration diagram when generating and updating the user master of the scheduler menu DB 14 in this system. In FIG. 4, the user information creation unit 200 includes an employee master database (DB) 201, a server DB table. Using 202 as an input, a user master of the scheduler menu DB 14 is generated or updated.
[0032]
The employee master database (DB) 201 holds at least information on all employees maintained by the personnel department, such as employee numbers, notes addresses, names (kanji, kana, and romaji), work locations, and affiliations. Yes.
[0033]
The server DB table 202 holds information including an office name, a server name, a database type, and a database location for each office, and is created in advance by an administrator.
Here, the server name is the name of the server that manages the database. The type of database is a code for distinguishing the database (schedule DB, scheduler menu DB, common equipment reservation DB, etc.) held by each business office in this system. The location of the database is the file name of the database corresponding to “database type”.
[0034]
When personal information different from personal information registered in the employee master DB 201 is set, the employee number is associated with a name (notation in kanji, kana, romaji), work location or affiliation, and the user ( Created by the administrator of this system as a user master of employees.
For example, “name” is used when you want to use your maiden name even if you are married and your family name changes. Also, “work location” and “affiliation” are used when working at a place different from personnel information when concurrently serving.
[0035]
Next, the operation of the user information creation unit 200 will be described.
(1) User master batch import processing
This option is executed when the user master is generated in the schedule menu DB 14 for the first time.
First, the user logs in to the system, authenticates that he / she is an administrator by the authentication DB 11, and then clicks a “user master batch import” button from the displayed option buttons.
For each employee, information of “employee number, notes address, name (notation in kanji, kana and roman letters), location and affiliation” is extracted from the employee master DB 201, and the employee number, notes address, name (kanji, kana) In addition, the work location and affiliation are written in the user master.
[0036]
Further, referring to the server DB table 202, the location of each database related to the schedule at the workplace is searched from the workplace of this employee (this workplace has the same name as the office), The server name, database type, and database location are written in the user master in correspondence with the employee number.
[0037]
(2) User master update process at any time
First, the user logs in to the system, authenticates that he / she is an administrator by the authentication DB 11, and then clicks the “update user master as needed” button from the displayed option buttons.
In this case, since the user master already exists, only a new employee or the like that exists in the employee master DB 201 but does not exist in the user master is newly generated. To update only the different parts of the user and write them to the user master.
[0038]
(3) User master periodic update process
As an agent of the scheduler menu DB 14, it is defined that the user master is periodically updated in accordance with the database update cycle of the personnel department of the employee master DB 201.
In this update item, as with the above-mentioned “update from time to time of user master”, information on new employees is added and a retirement flag is added, and the user master is updated for different parts of the user.
[0039]
(4) User master (selected user) update process
First, log in to the system, authenticate that the user is an administrator by the authentication DB 11, and then select the user that the administrator wants to update from the user master beforehand, and select “user master (selected user) from the option buttons. Click the "Update" button.
In this case, the user master is updated by referring to the employee master DB 201 only for the selected user. If the employee has retired, a retirement flag is set.
[0040]
(5) User master (selected user) initialization process
First, log in to the system, authenticate that the user is an administrator by the authentication DB 11, and then select the user that the administrator wants to update from the user master beforehand, and select “user master (selected user) from the option buttons. Click the “Initialize” button.
In this case, only the selected user is referred to the employee master DB 201 and the server DB table 202, and the user information of the user master is generated again. If the employee has retired, a retirement flag is set.
[0041]
Thus, in order to update the user master user information from the employee master DB 201, which is constantly updated as personnel information, at any time or periodically, when an employee joins or leaves the company, or contracts / changes / Even when deletion occurs, the user master can be maintained without individually registering, changing, or deleting the user.
[0042]
(B) Schedule creation
(1) Schedule registration
An explanation will be given of an example of schedule registration when a meeting is held in a group.
When a “my schedule” button 301 is clicked from the own schedule screen (see FIG. 3), a schedule registration screen as shown in FIG. 5 is displayed.
On this registration screen, enter the required meeting date, time, requirements, location, meeting target, contact mail necessity, etc. in the respective input fields, and click the execute button 304 to display a confirmation dialog. When “OK” is displayed, a schedule data update document is created, and the person who registered the schedule starts the agent immediately and the schedule is additionally registered in the schedule document for the conference month, and the schedule data is updated. A registration completion flag of the person's schedule document is set on the document (see FIG. 6).
[0043]
In addition, for a schedule of a target person other than the person himself / herself, the schedule agent is started every five minutes, and the schedule is additionally registered in the schedule document 13 of the target month in the schedule document of the meeting holding month, and the schedule data update document The registration completion flag of the schedule document of the target person is set in the mail, and if the transmission of the contact mail is specified, it is notified by mail that the meeting will be held.
[0044]
Since one month's schedule is expressed in one document, multiple people may update the same person's schedule document for the same month, but because there is no document exclusive control function, competing documents are created It will be done.
For this reason, an update document is created without directly updating the schedule document, and the registration of the update document is entrusted to the agent, thereby preventing the occurrence of a conflict document.
[0045]
In addition, the person's schedule is updated by the immediate agent, but since it takes a long time to register all the schedules of all other subjects, it is up to the regular agent to register the schedules of other subjects. Thus, the registration response time can be shortened without generating competing documents.
[0046]
On the other hand, if some of the target persons of this meeting are working at a different office from the person who registered to hold the meeting, create a schedule data update document for each other office, The update document is transmitted by e-mail to the schedule DB 13 of the other office where the subject person works (see FIG. 7).
This is because the registration agent of the schedule DB 13 of another office cannot be directly started, so registration of the update document is requested by e-mail, and the meeting of the target person whose received schedule DB 13 is in the update document is held by the agent. Add the schedule to the monthly schedule document.
[0047]
As a result, by writing a scheduled document of a person in another office by mail transmission, it can be guaranteed within the range of the mail transmission / reception function of the Domino environment without depending on the level of the server or the network environment. Therefore, it is possible to clearly distinguish the security guarantee range during registration and transmission / reception.
Response time can also be guaranteed at the Domino environment level.
[0048]
In addition, when the schedule in the schedule data update document is additionally registered in the schedule document for the conference month, if the capacity limit of one document is exceeded, a new document is generated and the header and high-speed are generated from the original document. Copy the display data and write the schedule to be added to a new document. At this time, information related to the schedule to be added is written in the header and the high-speed display data.
[0049]
For example, as shown in FIG. 8, when the capacity limit is reached when trying to register a three-day schedule, a new schedule document 401 is generated and the previous document 400 is added to the new document 401. Copy the header of (the last document if it was already divided into multiple documents).
Next, the 3 day schedule is written into a new document 401. At this time, the document number (document number of the new document 401) for which a three-day schedule exists is added to the document division index.
Further, referring to the schedule for 3 days, the work status of the day is graphically updated, the high-speed display data of the previous document 400 is updated, and the new document 401 is written. The graphics are created by allocating the respective color information for the schedule of the day, for example, during a meeting, double booking, going out, no reservation, vacation, etc. in the company.
[0050]
When the schedule for one month is registered in a plurality of divided documents, the last document divided is accessed,
-In the case of a personal schedule, refer to the document division index in the header of the document with the last document number of the specified year and month, read the document with the corresponding document number, obtain the schedule data for the required date, and display it To do.
In the case of group schedule list display, graphic information is extracted from the date of the high-speed display data of the document having the last document number of the specified year and month and displayed.
[0051]
In principle, it is possible to save the schedule data in one person / one month / one document, and to divide the data according to the capacity, thereby realizing a quick search by reducing the document size.
In addition, since the response time from acquiring the actual data of all group schedule subjects to converting them to graphics and displaying them can be reduced, a group schedule list with intuitive and easy-to-understand image data can be displayed with good response times. can do.
[0052]
(2) Reservation registration of common equipment
The reservation registration of common facilities (meeting rooms, equipment, etc.) managed at each office will be explained.
First, click the "to common equipment" button 303 from the menu screen shown in FIG. 3, and the reservation status list of the establishment that you want to reserve is displayed as shown in FIG. 9, so the common equipment to be reserved is reserved. Make sure it is not.
Next, when it is vacant, when the reservation registration button 500 is clicked on the common equipment list screen (see FIG. 9), the common equipment reservation registration screen on the reservation day as shown in FIG. 10 is displayed.
[0053]
From this registration screen, the required reservation time, selection of common equipment, requirements, usage category (internal use or distinction of visitors), the category of what the common equipment is used for and the target users, etc. are input fields. When the execution button 501 is clicked, a confirmation dialog is displayed, and when “OK” is clicked, the reservation is registered in the common facility reservation DB 15 and a reservation completion mail is transmitted to the registration executor and the user to be used. .
[0054]
Since the reservation registration document in the common facility reservation DB 15 records a reservation for one month, there is a high possibility that the same common facility will be reserved in the same time zone.
However, Notes does not have exclusive control when registering documents, so if you make a reservation for the same common equipment at the same time, it may cause conflicting documents or double booking. Exclusive control must be performed. In this case, when trying to reserve the common equipment for the first time, create a locked document of the common equipment on the system side, and if there is this locked document, exclude those who are going to register for reservation later. To do. That is, using this locked document, exclusive control of the common equipment is realized (see FIG. 11).
[0055]
Therefore, when the execution button 501 is clicked, if there is a locked document for the common equipment to be reserved, the “reservation work in progress” dialog is displayed to cancel execution of the reservation registration.
If there is no locked document, a locked document for the common equipment is generated and a confirmation dialog for reservation registration is displayed. When “OK” is clicked, the reservation is registered in the common equipment reservation DB 15. Then, a “reservation completion” dialog is displayed to the reservation registration executor, and other common users are notified by e-mail which common equipment has been reserved. Finally, the generated locked document is deleted, and the common facility is opened for the next reservation person.
Thereby, the double booking regarding a common installation can be prevented.
[0056]
(C) Group schedule list display
With reference to FIG. 12, a schedule list display in the case where personnel belonging to a group work at a plurality of offices will be described.
For example, the user (Mr. A) belongs to a group consisting of Mr. A, Mr. B, Mr. C, and Mr. D, and the work place of Mr. A and Mr. B is the business office A, and Mr. C and Mr. D. Let ’s say that his work place is office B.
In this case, it will be described that a schedule list such as “1 day display”, “1 week display”, or “1 month display” of all members belonging to the group is displayed.
[0057]
First, Mr. A uses the Web browser provided in the user terminal 17 to use the scheduler menu DB 14 of the office A. _A And the authentication DB 11 is authenticated, and the group display button 302 is clicked.
Next, the target person to display the group is specified. For example, when a group name or an individual as an associated person is selected from the user master DB 12 and, for example, “display date” and “display for one week” are designated, a group schedule list as shown in FIG. 3 is displayed.
[0058]
Scheduler menu DB14 _A Indicates which schedule DB the schedule of the designated display target person (Mr. A, Mr. B, Mr. C and Mr. D) is in the scheduler menu DB 14 _A Search for and retrieve.
Next, each schedule DB 13 having a schedule for each display target person is accessed, and high-speed display data for a specified year and month is taken out.
For example, for Mr. A and Mr. B, the schedule is set to the schedule DB 13 _A Take out from. For Mr. C and Mr. D, the schedule is set to schedule DB13. _B Take out from.
[0059]
Scheduler menu DB14 _A Converts the high-speed display data for one week including the specified date from the high-speed display data of the display target person thus taken out into a format to be displayed on the Web browser, and returns the converted data to the user terminal 17.
When the Web browser of the user terminal 17 displays the received data, a group schedule list as shown in FIG. 3 is displayed.
[0060]
A more detailed schedule can be displayed by selecting the target person and date from the list displayed as shown in FIG. In this case, when the date is selected, the data for high-speed display of the day is displayed, and when the target person is selected, the actual schedule data of the target person is referred instead of the data for high-speed display. To display.
[0061]
In this way, the response time for displaying the schedule of personnel belonging to the same office as the user himself / herself is fast, and the schedule of other offices referenced as necessary can be slightly different in response time, but the same user The list of group members' schedules across multiple offices can be displayed on the interface.
[0062]
The present invention is not limited only to the above-described embodiments. Each function constituting the schedule management system of the above-described embodiment is programmed, written in advance on a recording medium such as a CD-ROM, and this CD-ROM is stored in a medium driving device such as a CD-ROM drive mounted on a computer. Needless to say, the object of the present invention is achieved by storing these programs in a memory or a storage device of a computer and executing them.
In this case, the program itself read from the recording medium realizes the functions of the above-described embodiment, and the program and the recording medium recording the program also constitute the present invention.
[0063]
As a recording medium for storing the program, a semiconductor medium (eg, ROM, nonvolatile memory, etc.), an optical medium (eg, DVD, MO, MD, CD, etc.), a magnetic medium (eg, magnetic tape, flexible disk, etc.) Any of these may be used.
[0064]
Further, not only the functions of the above-described embodiment are realized by executing the loaded program, but also the above-described implementation by cooperating with the operating system or other application programs based on the instructions of the program. The case where the function of the form is realized is also included.
[0065]
In the case of distribution to the market, the program is stored and distributed on a portable recording medium, or stored in a storage device of a server computer connected via a communication network such as the Internet. It can also be transferred to a computer. In this case, the storage device of this server computer is also included in the recording medium of the present invention. In the computer, the functions of the above-described embodiments are realized by installing a program on a portable recording medium or a transferred program in a storage device connected to the computer and executing the installed program. Is done.
[0066]
The present invention is not limited to the above-described embodiments, and various modifications and corrections are possible without departing from the scope of the present invention.
[0067]
【The invention's effect】
As described above, according to the present invention, even if the number of users who use this system is a large number of users, the user information is updated from the employee master holding personnel information updated as needed to the user master as needed. Since the information is updated, it becomes easy to register / change / delete user information in the user master when an employee enters or leaves the company or a contract / change / delete of a person from a partner company occurs.
[Brief description of the drawings]
FIG. 1 is a block diagram showing the overall configuration of a schedule management system of the present invention.
FIG. 2 is a data structure diagram of a document for registering a schedule.
FIG. 3 is a display example of a group schedule list.
FIG. 4 is a functional configuration diagram when generating or updating a user master.
FIG. 5 is an example of a schedule registration screen.
FIG. 6 is a diagram for explaining the function of an agent when registering a schedule of employees of the same office.
FIG. 7 is a diagram for explaining the function of e-mail when registering the schedules of employees at other offices.
FIG. 8 is a diagram for explaining data movement when a scheduled document is divided;
FIG. 9 is an example of a common equipment list screen.
FIG. 10 is an example of a common facility reservation registration screen.
FIG. 11 is a diagram for explaining exclusive control at the time of common facility reservation.
FIG. 12 is a database related diagram when a group schedule list is displayed.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 10 ... Establishment, 11 ... Authentication DB, 13 ... Schedule DB, 14 ... Scheduler menu DB, 15 ... Common equipment reservation DB, 16 ... Administrator terminal, 17 ... User terminal, 18, 20 ... Network, 101 ... Header, 102 ... Schedule 103 ... High-speed display data 200 ... User information creation unit 201 ... Employee master DB 202 ... Server DB table 301 ... My schedule 302 ... Group display 303 ... Common equipment 304 ... Execute Button 400 ... Previous document 401 ... New document 500 ... Reservation registration button 501 ... Execution button

Claims (6)

In a schedule management system that manages the schedule of a large number of employees who belong to multiple offices, it retains personnel information consisting of at least employee numbers, email addresses, names, work locations, and affiliations of all employees that are updated at any time. An employee master DB, a schedule DB for each office, and a schedule DB for holding the schedule of employees belonging to each office, and the location information of the schedule DB managed by the office are associated with each other. For each employee who is a user of the system, user information that associates the employee number, e-mail address, name, work location, affiliation, and location information of the schedule DB used by the employee is stored for each server DB table to be stored. Based on the stored user master, the employee master DB and the server DB table, And a user information generation unit that performs batch generation and updating of the user master about membered, batch generation of the user master in the user information creation unit generates the user information for all employees, the user information generation unit The update of the user master is performed in synchronization with the update of the employee master DB, and for the employee that exists in the employee master DB but does not exist in the user master, the user information of the employee is stored. For the employee that is generated and exists in both the employee master DB and the user master, the user information is updated with respect to the email address of the employee and the location information of the schedule DB used by the employee, and the employee master DB Registered retired employees are also updated as retired employees in the user master. Schedule management system which is characterized in that. The schedule management system according to claim 1, wherein the user information creation unit is operated as required by an administrator of the system, and the employee exists in the employee master DB but does not exist in the user master. Generates the user information of the employee, and updates the employee master DB and the user master both for the employee email address and the location information of the schedule DB used by the employee, A retired employee registered in the employee master DB is also updated as a retired employee in the user master . The schedule management system according to claim 1, wherein an employee to be updated is selected and the user information creation unit is operated, and for an employee that has both the employee master DB and the user master, the email address of the employee and the employee A schedule management system in which location information in a schedule DB used by an employee is updated, and a retired employee registered in the employee master DB is also updated as a retired employee in the user master . 2. The schedule management system according to claim 1, wherein an employee to be updated is selected and the user information creation unit is operated to regenerate the user information of the employee based on the personnel information and the server DB table. A schedule management system characterized in that the user master is replaced. Computer program for causing the functions as each section of the schedule management system according to any one of claims 1 to 4. A computer-readable recording medium on which the program of the schedule management system according to claim 5 is recorded.

Images