JP2015201114A - Work management device, and meal charge management device, meal charge management method and meal charge management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable registered work that is associated with dates in a calendar to be simply performed.SOLUTION: The work management device is provided with a control unit for executing predetermined processing, and a storage unit for storing predetermined information, the storage unit having work definition information in which work content and a scheduled period of work execution for work relating to a predetermined management job are associated with each other, the control unit generating calendar information in which a predetermined icon is displayed on a scheduled date for executing the work, generating, upon receiving a selection of the icon, screen information for receiving an execution command for the work that is scheduled to be executed on the date on which the selected icon is displayed, and executing, upon receiving the execution command, a predetermined processing that can be executed by a computer according to the work.

Description

  The present invention relates to a work management apparatus.

  Patent Document 1 discloses an information processing method that facilitates management of data commonly handled by a plurality of members. Such a method displays a mark storing data at the position of the date when the data is stored in the configuration of the calendar representing the date. In addition, the mark displays a different mark based on the type of data. The mark functions as an icon, and the contents of the data are displayed by clicking on the icon.

JP 2001-101305 A

  In the method of Patent Document 1, data is stored in association with a date on a calendar, and a mark indicating that the data is stored on the date is displayed on the calendar. However, the method of this document only displays the contents of data when a mark is clicked. For example, when a predetermined work list is registered in association with the date, this list is only displayed.

  Therefore, an object of the present invention is to provide a lunch expense management apparatus that can more easily perform operations registered in association with calendar dates.

  In order to solve the above-described problems, a work management apparatus according to the present invention includes a control unit that executes predetermined processing and a storage unit that stores predetermined information, and the storage unit performs work related to a predetermined management task. The work definition information associated with the work content and the scheduled work execution period is generated, and the control unit generates calendar information displaying a predetermined icon on the scheduled work execution date, and accepts selection of the icon And screen information for receiving an execution instruction for the work whose scheduled date is the date on which the icon for which the selection has been received is displayed, and when the execution instruction is received, a predetermined process that can be performed by the computer according to the work Execute.

  According to the work management device of the present invention, the work registered in association with the date of the calendar can be performed more easily.

It is the schematic which showed an example of the lunch expense management system which is one of the representative examples of the work management system which concerns on one Embodiment of this invention. It is the figure which showed an example of the functional block which showed each function structure which the server apparatus which concerns on one Embodiment of this invention, an operator terminal, and a school terminal has. It is the figure which showed an example of the work definition information in one Embodiment of this invention. It is the figure which showed an example of the icon information which concerns on one Embodiment of this invention. It is the figure which showed an example of the hardware constitutions of the server apparatus which concerns on one Embodiment of this invention, an operator terminal, and a school terminal. It is the flowchart which showed the flow of the lunch expense management process performed with the server apparatus which concerns on one Embodiment of this invention. It is the flowchart which showed the flow of the calendar information generation process which concerns on one Embodiment of this invention. FIG. 8A is a screen example showing an example of a menu screen according to an embodiment of the present invention. FIG. 8B is a screen example showing an example of an irregular menu screen. It is the example of a screen which showed an example of the input screen used for work registration concerning one embodiment of the present invention. It is the example of a screen which showed an example of the regular menu screen concerning one embodiment of the present invention. FIG. 11A is a diagram showing an example of a calendar menu screen according to an embodiment of the present invention. FIG. 11B is a screen example showing an example of a work list screen according to an embodiment of the present invention. It is the figure which showed an example of the input screen which concerns on one Embodiment of this invention. FIG. 13A is a diagram showing an example of common work definition information according to another embodiment of the present invention. FIG. 13B is a diagram showing an example of specific work definition information according to another embodiment of the present invention. FIG. 14A is a diagram showing an example of a calendar menu screen according to another embodiment of the present invention. FIG. 14B is a diagram showing an example of a work list screen according to another embodiment of the present invention. It is the flowchart which showed the flow of the calendar information generation process which concerns on other embodiment of this invention. It is the figure which showed the calendar information which concerns on other embodiment of this invention. FIG. 17 is a diagram illustrating an example of the number of meals registration management information. FIG. 18A is a diagram showing an example of a lunch implementation date registration screen. FIG. 18B is a diagram showing an example of the number of eating registration screen. FIG. 19A is a diagram showing an example of a screen example on which calendar information generated according to this modification is displayed. FIG. 19B is a diagram illustrating an example of an icon indicating that the number of eating is not registered.

  Hereinafter, each embodiment of the present invention will be described.

<First embodiment>
FIG. 1 is a schematic diagram showing an example of a school lunch management system 1000 which is one of representative examples of the work management system according to the first embodiment of the present invention. As illustrated, the system 1000 includes a server device 100 that functions as a work management device, an operator terminal 200, and a school terminal 300. The server device 100, the operator terminal 200, and the school terminal 300 are connected to each other via a network N such as the Internet so that they can communicate with each other. In this embodiment, the work management system is applied to the school lunch management business that centrally manages the school school lunch expenses. However, the target of the system configuration is not necessarily limited to the school lunch management business. It is not something that can be done. For example, it can also be applied to the cost management of people who make up a given community (for example, the cost management of PTA membership fees, supplementary teaching material costs, etc. of each school, the management of operating costs of facilities operated and managed by local governments, etc.) .

  The server apparatus 100 is a school lunch management apparatus that provides a service related to a school lunch management service to the operator terminal 200 and the school terminal 300. Specifically, the server device 100 accepts registration of information such as the work contents related to the management of lunch expenses and the scheduled execution period of the work (the period from the planned execution date to the execution deadline). In addition, the server device 100 generates calendar information including an icon indicating a progress status indicating the progress status of the work. In addition, the server device 100 accepts registration of information related to a person who is charged for school lunch (for example, a student who uses school lunch and a cafeteria staff member). Further, the server device 100 creates a predetermined notification document such as a reminder for a eater who has not paid the school lunch fee.

  The operator terminal 200 is used by a person in charge (operator) of a prefectural or city school board, and is used for a task of centralized management of school lunch expenses. Specifically, the operator terminal 200 receives input of the work contents and the scheduled execution period of the work related to the management of lunch expenses from the operator, and transmits these pieces of information to the server apparatus 100. Further, the operator terminal 200 displays the calendar information acquired from the server device 100. In addition, the operator terminal 200 receives an input of information related to a person who is billed for a school lunch, an instruction to calculate a school lunch, and the like, and transmits the information to the server device 100.

  The school terminal 300 is an apparatus that is installed in each school and accepts input of information related to a meal eater such as students and teachers, instructions for calculating school lunch costs, and the like from a user (for example, a teacher). The school terminal 300 transmits the received information to the server device 100.

  FIG. 2 is a diagram illustrating an example of functional blocks showing the functional configurations of the server device 100, the operator terminal 200, and the school terminal 300. The server device 100 includes a control unit 101 and a storage unit 102. Further, the control unit 101 includes an input reception unit 103, an output processing unit 104, a school lunch cost calculation unit 105, a work definition information update unit 106, a calendar information generation unit 107, and a notification document creation unit 108. It is. In addition, the storage unit 102 includes eater information 110, number of eaters information 111, school lunch information 112, work definition information 400, and icon information 500.

  The eater information 110 is information that stores information related to a eater. Specifically, the eater information 110 stores the school name, name, grade, class, address, school account debit account number, etc. of the students and teachers who are eaters. The eater information 110 is updated by an operator or a faculty member as part of the work related to the management of lunch expenses.

  The number of meals information 111 is information in which the number of meals for a predetermined period (for example, one month of each month) is stored in association with the person who eats. Note that the number of meals information 111 is updated by an operator or a staff member as part of the work related to the school lunch fee management work.

  The school lunch cost information 112 is information in which a school lunch cost for a predetermined period (for example, one month of each month) is stored in association with a eater. The server apparatus 100 calculates the school lunch cost information 112 by executing a school lunch cost calculation work program in response to a request from the operator terminal 200 or the school terminal 300.

  The work definition information 400 is information that stores information related to work contents of various works related to the management work of school lunch expenses, scheduled work execution periods, and the like. FIG. 3 is a diagram showing an example of the work definition information 400. The work definition information 400 includes an scheduled execution date column 401, an implementation deadline column 402, a work content column 403, an implementer column 404, an implementation month / day column 405, a work status column 406, and an icon identification information column 407. And a plurality of records associated with each other.

  The date stored in the scheduled execution date field 401 is information indicating the scheduled execution date of the work stored in the work content field 403. The date stored in the execution deadline column 402 is information indicating the execution deadline date of the work stored in the work content column 403. The work stored in the work content column 403 is information indicating the work content related to the management work of school lunch expenses. For example, information specifying various work contents such as “new student registration”, “food number registration”, “sibling registration”, “lunch cost calculation”, “preparation of reminder” is stored in the work content column. It should be noted that operations such as new student registration and sibling registration are operations for updating the eater information 110. In addition, the operation of registering the number of eating is an operation for updating the number of eating information 111. Moreover, the work of calculating the school lunch cost is a work for updating the school lunch cost information 112.

  The name stored in the performer column 404 is information indicating the performer of the work stored in the work content column 403. The date stored in the execution month / day column 405 is information indicating the date when the work in the work content column 403 was performed. The identification information stored in the work status column 406 is information indicating the work in progress status of the work content column 403. For example, numerical values from 1 to 3 are stored in the work state column 406, and each numerical value corresponds to a work state such as “unprocessed”, “processed”, and “midway”. The character string information stored in the icon identification information column 407 is information for identifying an icon displayed in the calendar information.

  The icon information 114 is information that stores an icon or the like that visually indicates the progress status of the work related to the school lunch management work. FIG. 4 is a diagram illustrating an example of the icon information 114. The icon information 500 has a record in which an identification ID field 501, a progress status field 502, and an icon field 503 are associated with each other.

  The character string stored in the identification ID column 501 is information for identifying the icon and the progress status, and is identification information common to the character string stored in the work display column 406 of the work definition information 400. The character string stored in the progress status column 502 is information indicating the progress status indicated by each icon. The progress status stores, for example, “waiting for work”, “work completed”, “work not completed”, “date of deadline”, “exceeding deadline”, and the like. “Waiting for work” is a progress status indicating that the scheduled execution date of the work is a date earlier than the date when the calendar is displayed, that is, the date when the calendar is generated (hereinafter referred to as the calendar day). The work completion is a progress status indicating that all work included in the date after the scheduled execution date of the calendar and before the execution deadline has been completed. Work incomplete is a progress status indicating that there is an incomplete work among the work included in the date after the scheduled execution date of the calendar and before the implementation deadline. The deadline date is a progress status indicating that the date on the calendar day corresponds to the deadline date of the work and there is an incomplete work. The deadline exceeded is a progress status indicating that the date on the calendar day is a date after the implementation deadline and there is an incomplete work.

  The icon stored in the icon column 503 is information for specifying an icon to be displayed in the calendar information. The icon column 503 stores icons having different shapes depending on the progress status stored in the progress status column 502.

  The input receiving unit 103 is a functional unit that receives input of instructions and information from the operator terminal 200 and the school terminal 300. Specifically, the input accepting unit 103 accepts input from the operator terminal 200 or the school terminal 300 such as work contents, a registration instruction for the scheduled execution period, a display instruction for calendar information, and information about a eater. In addition, the input receiving unit 103 instructs a predetermined function unit corresponding to the received instruction to execute the process. Further, the input receiving unit 103 passes information acquired from the operator terminal 200 or the school terminal 300 to a corresponding predetermined function unit.

  The output processing unit 104 is a functional unit that displays predetermined screen information on the operator terminal 200 or the school terminal 300. Specifically, the output processing unit 104 generates predetermined screen information such as a menu screen, an input screen, and calendar information.

  The school lunch cost calculation unit 105 is a functional unit that calculates school lunch costs. Specifically, the school lunch cost calculation unit 105 calculates the school lunch cost for each predetermined person from the number of meals information 111, and stores the calculated school lunch cost in association with each person in the school meal cost information 112.

  The work definition information update unit 106 is a functional unit that updates the work definition information 400. Specifically, when the work definition information update unit 106 acquires the work content and the scheduled work execution period from the operator terminal 200 or the school terminal 300, the work definition information update unit 106 stores these information in a predetermined column of the work definition information 400. Also, the work definition information update unit 106 acquires information indicating the implementer, the implementation date, and the work status from the operator terminal 200 or the school terminal 300 when the work is completed, and the obtained information is stored in the work definition information 400. Store in a predetermined field.

  The calendar information generation unit 107 is a functional unit that generates calendar information including an icon indicating the work progress status. Specifically, the calendar information generation unit 107 specifies the work progress status according to the calendar information generation date (calendar day), the scheduled execution period of the work, and the work status of the work, and the identified progress status Calendar information in which an icon corresponding to is superimposed and displayed on the scheduled operation date is generated.

  The notification document creation unit 108 is a functional unit that creates various documents related to management of school lunch expenses. For example, the notification document creation unit 108 creates a reminder for payment to a eater who has not paid the school lunch fee or the guardian. Specifically, the notification document creation unit 108 specifies information included in the dunning letter, that is, the name, address, lunch cost, etc. of the eater from the eater information or the lunch cost information 112, and prints the dunning letter information. Create the reminder information entered in the format.

  The communication unit is a functional unit for transmitting / receiving information to / from external devices other than the server device 100 (for example, the operator terminal 200 and the school terminal 300).

  Next, functional blocks of the operator terminal 200 will be described. The operator terminal 200 includes an input unit 201, a display unit 202, a storage unit 203, and a communication unit 204.

  The input unit 201 is a functional unit that receives an instruction input of information from an operator via a predetermined input device such as a mouse, a keyboard, and a touch panel.

  The display unit 202 is a functional unit that displays screen information acquired from the server device 100.

  The storage unit 203 is a functional unit that stores various information used for processing of the operator terminal 200.

  The communication unit 204 is a functional unit for transmitting and receiving information to and from external devices other than the operator terminal 200 (for example, the server device 100 and the school terminal 300).

  Next, functional blocks of the school terminal 300 will be described. The school terminal 300 includes an input information reception unit 301, an output information processing unit 302, an information storage unit 304, and an information communication unit 303.

  The input information reception unit 301 is a functional unit that receives an instruction input of information from a user of the school terminal 300 via a predetermined input device such as a mouse, a keyboard, and a touch panel.

  The output information processing unit 302 is a functional unit that displays screen information acquired from the server device 100.

  The information storage unit 304 is a functional unit that stores various information used for processing of the operator terminal 200.

  The information communication unit 303 is a functional unit for transmitting / receiving information to / from external devices other than the operator terminal 200 (for example, the server device 100 and the school terminal 300).

  The functional blocks of the server device 100, the operator terminal 200, and the school terminal 300 have been described above.

  FIG. 5 is a diagram illustrating an example of a hardware configuration of the server device 100, the operator terminal 200, and the school terminal 300.

  The server apparatus 100 is a computer such as a personal computer or a workstation.

  The server device 100 includes an arithmetic device 151, a main storage device 152, an external storage device 153, a communication device 154, and a bus 155 that connects the devices to each other.

  The arithmetic device 151 is an arithmetic device such as a CPU (Central Processing Unit), for example.

  The main storage device 152 is a memory device such as a RAM (Random Access Memory), for example.

  The external storage device 153 is a non-volatile storage device such as a hard disk device or a flash memory, for example.

  The communication device 154 is a communication unit that transmits / receives information to / from an external device.

  The input reception unit 103, the output processing unit 104, the school lunch cost calculation unit 105, the work definition information update unit 106, the calendar information generation unit 107, and the notification document creation unit 108 of the server device 100 are executed by a program that causes the arithmetic device 151 to perform processing. Realized. This program is stored in the main storage device 152 or the external storage device 153, loaded onto the main storage device 152 for execution, and executed by the arithmetic device 1. In addition, the communication device 154 implements the communication unit 120. The main storage device 152 and the external storage device 153 implement the storage unit 102.

  The operator terminal 200 is, for example, a computer such as a personal computer or a workstation.

  The operator terminal 200 includes an arithmetic device 211, a main storage device 212, an input device 213, an external storage device 214, a display device 215, a communication device 216, and a bus 216 that interconnects the devices. Have.

  The arithmetic device 211 is an arithmetic device such as, for example.

  The main storage device 212 is a memory device such as, for example.

  The input device 213 is a device for accepting user instruction input such as a keyboard, a mouse, and a touch panel.

  The external storage device 214 is, for example, a nonvolatile storage device such as a hard disk device or a flash memory.

  The display device is a device that displays image information 215, for example, a liquid crystal display.

  The communication device 216 is a communication unit that transmits / receives information to / from an external device.

  The input unit 213 and the display unit 215 of the operator terminal 200 are realized by a program that causes the arithmetic device 211 to perform processing. This program is stored in the main storage device 212 or the external storage device 214, loaded onto the main storage device 212 for execution, and executed by the arithmetic device 211. Further, the communication device 216 implements the communication unit 204. In addition, the main storage device 212 and the external storage device 214 implement the storage unit 203.

  The school terminal 300 is a computer such as a personal computer or a workstation.

  The school terminal 300 includes an arithmetic device 311, a main storage device 312, an input device 313, a display device 314, an external storage device 315, a communication device 316, and a bus 317 that interconnects the devices. .

  The arithmetic device 311 is an arithmetic device such as a CPU, for example.

  The main storage device 312 is a memory device such as a RAM, for example.

  The input device 313 is a device for accepting user instruction input such as a keyboard, a mouse, and a touch panel.

  The display device 314 is a device that displays image information, such as a liquid crystal display.

  The external storage device 315 is, for example, a nonvolatile storage device such as a hard disk device or a flash memory.

  The communication device 316 is a communication unit that transmits / receives information to / from an external device.

  The input information receiving unit 301 and the output information processing unit 302 of the school terminal 300 are realized by a program that causes the arithmetic device 311 to perform processing. This program is stored in the main storage device 312 or the external storage device 315, loaded on the main storage device 312 for execution, and executed by the arithmetic device 311. Further, the communication device 316 implements the information communication unit 303. In addition, the main storage device 312 and the external storage device 315 implement an information storage unit 304.

  The hardware configurations of the server device 100, the operator terminal 200, and the school terminal 300 have been described above.

[Description of operation]
Next, processing executed in the school lunch cost management system 1000 will be described. FIG. 6 is a flowchart showing the flow of the school lunch management process executed by the server device 100. The lunch expense management process is started when the operator terminal 200 logs in to the server device 100, for example.

  When the operator logs in to the server apparatus 100 via the operator terminal 200, the output processing unit 104 displays a menu screen on the operator terminal 200 (step S001). FIG. 8A is a screen example showing an example of the menu screen 600. In the menu screen 600, as a main menu, 1. Regular work (calendar), 2. 2. irregular work; Menu items such as work registration and an execution button 601 are displayed.

  Next, the input receiving unit 103 determines whether or not a regular work (calendar) has been selected (step S002). If the regular work (calendar) is not selected (No in step S2), the input receiving unit 103 determines whether or not the irregular work is selected (step S009). If the irregular work is not selected (No in step S009), the output processing unit 104 displays an input screen used for work registration on the operator terminal 200 and accepts input of information (step S012). FIG. 9 is a screen example showing an example of the input screen 630 used for work registration. The work registration input screen 630 is provided with a work content input field 631, an execution date input field 632, and an execution deadline input field 633.

  Next, the work definition information update unit 106 updates the work definition information 400 using the information input in each input field (step S013). Specifically, the work definition information updating unit 106 sets the information input in the work content input field 631, the scheduled execution date input field 632, and the execution deadline date input field 633, respectively, in the predetermined fields of the work definition information 400. To store. When the work definition information 400 is updated, the work definition information update unit 106 returns the process to step S001.

  If it is determined in step S009 that irregular work has been selected (Yes in step S009), the output processing unit 104 displays an irregular menu screen on the operator terminal 200, and selects menu items for irregular work. Is received (step S010). FIG. 8B is a screen example showing an example of the irregular menu screen 610. The irregular menu screen 610 displays predetermined menu items relating to work that occurs irregularly, such as transfer student registration. The irregular work may be stored in the storage unit 102 in advance, or may be generated in the storage unit based on an input from the operator terminal 200. Further, the work definition information 400 may be stored together with information for identifying a regular work.

  Next, the input receiving unit 103 executes a predetermined process corresponding to the selected menu item for the irregular work (step S011). For example, when the selected menu item is transfer student registration, the output processing unit 104 determines the input screen of the eater information 110, that is, the transfer student's school name, school year, class, name, address, school lunch withdrawal account number, etc. An input screen for accepting the input of the information is displayed on the operator terminal 200, and the input of the information is accepted. Moreover, the input reception part 103 stores the input information in the eater information 110, and returns a process to step S. FIG.

  If it is determined in step S002 that the regular work has been selected (Yes in step S002), the calendar information generating unit 107 displays a regular menu screen on the operator terminal 200 and selects a month for displaying the work schedule. Accept. FIG. 10 is a screen example showing an example of the regular menu screen 640. On the regular menu screen 640, months for displaying work schedules are listed.

  Next, the calendar information generation unit 107 generates calendar information for the month for which selection has been accepted (step S003). FIG. 7 is a flowchart showing the flow of the calendar information generation process. When such processing is started, the calendar information generating unit 107 identifies a record including the date of the selected month from the scheduled work date from the work definition information (step S021). Further, the calendar information generation unit 107 acquires the date of the calendar day from a predetermined function unit (not shown) of the operator terminal 200 (step S022).

  Next, the calendar information generating unit 107 specifies the work progress status of the specified record (step S023). For example, the calendar information generation unit 107 specifies that the work progress status of the record in which the date prior to the calendar day is stored on the scheduled work execution date is waiting for work. In this case, the calendar information generating unit 107 identifies the identification ID of the icon indicating work waiting from the icon information 114 and stores it in the icon identification information column 407 of the work definition information 400.

  In addition, when the date on the calendar day is included in the date after the scheduled implementation date and before the implementation deadline date, the calendar information generating unit 107 identifies the information stored in the work status column 406 of the record. When the identification information indicating that processing has been completed is stored in the work status column 406, the work progress status of the record specifies that the work is completed. In this case, the calendar information generation unit 107 identifies an icon identification ID indicating work completion from the icon information 114 and stores it in the icon identification information column 407 of the work definition information 400. On the other hand, when identification information indicating unprocessed or halfway is stored in the work status column 406, the calendar information generation unit 107 specifies that the work progress status of the record is incomplete. In this case, the calendar information generation unit 107 identifies the identification ID of the icon indicating work incomplete from the icon information 114 and stores it in the icon identification information column 407 of the work definition information.

  In addition, when the date on the calendar day corresponds to the implementation deadline date, the calendar information generation unit 107 identifies information stored in the work status column 406 of the record. When the identification information indicating that processing has been completed is stored in the work status column 406, the work progress status of the record specifies that the work is completed. In this case, the calendar information generation unit 107 identifies an icon identification ID indicating work completion from the icon information 114 and stores it in the icon identification information column 407 of the work definition information 400. On the other hand, when identification information indicating unprocessed or halfway is stored in the work status column 406, the calendar information generating unit 107 specifies that the work progress status of the record is the deadline date. In this case, the calendar information generation unit 107 specifies the identification ID of the icon indicating the deadline date from the icon information 114 and stores it in the icon identification information column 407 of the work definition information 400.

  In addition, when the date on the calendar day is a date after the implementation deadline, the calendar information generation unit 107 identifies information stored in the work status column 406 of the record. When the identification information indicating that processing has been completed is stored in the work status column 406, the work progress status of the record specifies that the work is completed. In this case, the calendar information generation unit 107 identifies an icon identification ID indicating work completion from the icon information 114 and stores it in the icon identification information column 407 of the work definition information 400. On the other hand, when identification information indicating unprocessed or halfway is stored in the work status column 406, the calendar information generating unit 107 specifies that the work progress status of the record is past the deadline. In this case, the calendar information generating unit 107 specifies an identification ID of an icon indicating that the deadline has been exceeded from the icon information 114 and stores it in the icon identification information column 407 of the work definition information 400.

  Next, when there are a plurality of records in which the same date is stored among the identified records, the calendar information generation unit 107 sets the progress status of the icon displayed in the calendar information as a representative to 1 Are identified (step S024). It is assumed that the display priority is set in advance in the order of waiting for work <work completed <work not completed <deadline date <deadline date exceeded.

  The calendar information generation unit 107 applies the progress status specified by the identification ID stored in the icon identification information column 407 of all records having the same scheduled execution date to the display priority. Then, the icon indicating the progress status of the record with the highest display priority is specified as the representative icon of all these records. For example, in the case of the work definition information 400 shown in FIG. 3, there are three records with March 22 as the scheduled implementation date. In addition, it is assumed that the progress statuses specified by the identification IDs stored in these records are work completion, work incomplete, and deadline date. In this case, the calendar information generation unit 107 specifies an icon indicating the deadline date with the highest display priority as an icon to be superimposed on the date of March 22 of the calendar information.

  In addition, the calendar information generation unit 107 specifies a record having no other record in which the same date is stored on the scheduled work execution date by the identification ID stored in the icon identification information 407 of the record. Identify the progress status icon.

  In addition, the calendar information generation unit 107 generates calendar information in which the identified icon is superimposed and displayed on the scheduled execution date (step S025). When the calendar information is generated, the calendar information generation unit 107 ends the calendar information generation process and proceeds to the process of step S004 in FIG.

  Next, the output processing unit 104 displays calendar information and accepts selection of an icon (step S004). Specifically, the output processing unit 104 displays a calendar menu screen including calendar information on the operator terminal 200 and accepts selection of an icon. FIG. 11A is a diagram showing an example of the calendar menu screen 650. In the calendar information, a predetermined icon indicating the progress status of the work is displayed on each date corresponding to the scheduled work execution date.

  When the icon is selected, the output processing unit 104 displays a work list screen 660 shown in FIG. 11B on the operator terminal 200 (step S005). The work list screen 660 displays a continuous work instruction button 661 and a single work instruction button 662 for instructing whether the work is a continuous work or a single work, and a work list table 663. In addition, the work list table 663 includes an order field, a work content field, an execution schedule date field, an execution deadline field, an implementer field, an execution month / day field, and an operation status field. When generating the work list table, the output processing unit 104 displays predetermined information such as the work content of the record in which the date on the calendar displaying the selected icon is stored in the scheduled execution date column 401 as work definition information. Obtained from 400 and stored in the work list table 663.

  Next, each functional unit executes a predetermined process corresponding to the selected work (step S006). Specifically, when the single work instruction button 662 is pressed in a state where any one record of the work list table 663 is selected, a predetermined functional unit corresponding to the work of the record of the selected work list table 663 is selected. Executes a predetermined process. For example, when the work of the selected record is new student registration, the output processing unit 104 displays an input screen 670 shown in FIG. 12A on the operator terminal 200, and accepts registration of information on new students. In addition, for example, when the work of the selected record is school lunch cost calculation, the school lunch cost calculation unit 105 calculates the school lunch cost using predetermined information.

  Note that the operator presses an end button 671 when ending the input of information regarding the new student. On the other hand, the operator presses the registration continuation button 672 when continuing to input information on another new student. The input receiving unit 103 stores the input information in predetermined information such as the eater information 110, regardless of whether any button is pressed.

  In addition, when detecting that the end button 671 is pressed, the input receiving unit 103 displays the work list screen 660 again, and receives input of the implementer, the implementation date, and the work state (step S007). In the work status column, for example, a progress status such as processed or halfway is input. When receiving the input of these pieces of information, the work definition information updating unit 106 stores the input information in the work definition information 400 and updates the work definition information (step S008). The work definition information update unit 106 returns the process to step S001.

  In step S006, when the pressing of the continuous work instruction button 661 is accepted, the output processing unit 104 continuously executes the processes related to the work of each record stored in the work list table 663. Specifically, the output processing unit 104 specifies the work to be performed first based on the order stored in the order column. In the example of FIG. 11B, new student registration is specified. Further, the output processing unit 104 displays a new student registration screen shown in FIG. 12A and accepts registration of information related to new students.

  When the end button 671 is pressed on the input screen, the output processing unit 104 specifies the next work to be performed based on the information stored in the order column of the work list table 663. In the case of FIG. 11B, the output processing unit 104 specifies that the next operation to be performed is the number of meals to be registered. Further, the output processing unit 104 displays the number of meals registration screen 680 shown in FIG. 12B and accepts registration of the number of meals.

  In addition, when the end button 681 is pressed on the number of meals registration screen 680, the output processing unit 104 determines that the next operation is a meal cost calculation based on the information stored in the order column of the operation list table 663. Identify. In this case, the school lunch cost calculation unit 105 calculates the school lunch cost using predetermined information.

  When the continuous work instruction button 661 is pressed, the work of each record stored in the work list table 663 is continuously executed in this way.

  When all the operations stored in the operation list table 663 have been completed, the output processing unit 104 displays an input screen for the operator, the operation date, and the operation status, as described above. Is received (step S007). When receiving the input of such information, the work definition information update unit 106 stores the input information in the work definition information 400 and updates the work definition information (step S008). The work definition information update unit 106 returns the process to step S001.

  In the above, the lunch expense management apparatus which concerns on 1st embodiment was demonstrated. According to such a school lunch management system, the work registered in association with the date of the calendar can be performed more easily. In particular, an operator who performs management of school lunch expenses can confirm a scheduled work list by selecting an icon displayed on the calendar. In addition, by pressing an instruction button displayed in the work list, a predetermined process that can be performed by the computer corresponding to the work is executed, so that the operator can start the calendar without starting a separate program for the work. It can be performed in a series of flow from display to execution of work.

  Moreover, according to the lunch expenses management apparatus which concerns on 1st embodiment, since an icon is displayed on a calendar, it is possible to prevent forgetting work. Further, since the icon displays the progress status of the work, the operator can determine the work to be prioritized according to the status.

  In the above-described embodiment, the operator registers the information on the number of eaters at each school and the number of meals, etc., in the server device 100 via the operator terminal 200. The form which registers the information and the number of meals to the server apparatus 100 may be sufficient. In this case, the server apparatus 100 displays a predetermined input screen on the school terminal 300 of each school and accepts input of such information. Moreover, the input reception part 103 of the server apparatus 100 stores the information acquired from each school in the eater information 110 and the eating number information 111, for example.

  Moreover, you may make it display the calendar information containing the icon which shows the progress status of the predetermined | prescribed work performed on the school terminal 300 on the school terminal 300. FIG. In this case, the work definition information 400 associated with each school may be stored in the storage unit 102.

<Second embodiment>
The server apparatus 100 that is a school lunch expense management apparatus according to the present embodiment includes a common scheduled execution date that is set in advance for work common to each school, and each of the common tasks that is different from the common scheduled schedule date. The difference between the school-specific scheduled execution date is obtained, the school-specific scheduled implementation date is specified, and calendar information displaying an icon indicating the work progress status on the scheduled implementation date is generated. The work common to each school is a work that usually occurs at the same time every year at any school (for example, registration of a new student, transfer of a teacher, etc.). In addition, since such work basically occurs every year, for example, a common scheduled execution date is registered in the server apparatus 100 as work common to each school by a person in charge (operator) of the school board. And On the other hand, there are schools that cannot perform common work on a common scheduled date set in advance by an operator (for example, because work time cannot be taken due to school events). Therefore, the faculty member registers the school-specific scheduled implementation date in the server device 100 for common work. In this case, the server apparatus 100 obtains the difference between the common scheduled execution date and the scheduled implementation date unique to each school, which is different from the common scheduled execution date, and performs the work on the scheduled execution date unique to each school. Calendar information that displays an icon indicating the progress status of is generated. Note that the basic configurations of the server device 100, the operator terminal 200, and the school terminal 300 according to the present embodiment are the same as those of the above-described embodiment, and therefore only the differences will be described.

  Two types of work definition information are stored in the storage unit 102 of the server device 100 according to the present embodiment. Specifically, the storage unit 102 stores common work definition information and unique work definition information. FIG. 13A is a diagram showing an example of the common work definition information 700. As shown in the figure, the configuration of each item column is the same as that of the above-described work definition information 400, and thus description thereof is omitted. The common work definition information 700 is information in which common work is registered in each school. Such common work definition information 700 is information that is registered in advance by the operator for work common to each school that occurs every year. It is assumed that common work definition information 700 is stored in the storage unit 102 for each school.

  FIG. 13B is a diagram illustrating an example of the unique work definition information 750. The unique work definition information 750 is work definition information unique to each school, and is generated and updated by input from a teacher through the school terminal 300. The unique work definition information 750 has the same configuration as the work definition information 400 described above except that it has a common scheduled execution date column 751. The information stored in the common execution scheduled date column 751 is information indicating the scheduled execution date stored in the common work definition information 700 for the same work content. The unique work definition information 750 is information unique to each school, and is associated with each school.

  Here, generation of the unique work definition information 750 will be described. FIG. 14A is a diagram showing an example of a calendar menu screen 800 displayed on the school terminal 300. The calendar menu screen 800 displays the scheduled work dates and icons common to each school. As shown in the figure, for example, when changing the scheduled execution date of the common work set on March 10 to the scheduled execution date unique to the school, the faculty member selects the displayed icon.

  When receiving an instruction input from the school terminal 300, the output processing unit 104 of the server apparatus 100 displays a work list screen on the school terminal 300. FIG. 14B is a diagram showing an example of a work list screen 810 displayed on the school terminal 300. The work list screen 810 is the same as that of the above-described embodiment except that a button 811 for performing an input instruction for the specific scheduled execution date is provided.

  When the specific execution date button 811 is pressed in a state where any one record included in the work list table 812 is selected, the output processing unit 104 is a predetermined for inputting the scheduled execution period of the common work related to the change. Is displayed on the school terminal 300. In addition, when the input receiving unit 103 receives the input of the scheduled execution date (for example, March 12) and the execution deadline related to the change, the work definition information updating unit 106 generates unique work definition information 750. Specifically, the work definition information updating unit 106 sets the work content and the work execution scheduled date of the record selected from the work list table 810, respectively, and the common execution scheduled date field 751 and the work content field of the unique work definition information 750, respectively. Stored in 754. Further, the scheduled execution date and the implementation deadline date related to the change that has been accepted are stored in the scheduled execution date column 752 and the implementation deadline column 753 of the unique work definition information 750, respectively.

  Next, a calendar information generation process using the unique work definition information 750 will be described. FIG. 15 is a flowchart showing a flow of calendar information generation processing according to the present embodiment. This flow is started when a display request for calendar information is received from the school terminal 300 of the school with which the specific work definition information 750 is associated.

  The calendar information generating unit 107 specifies a record including the date of the month for which the display request has been received from the scheduled work date from the common work definition information 700 (step S031).

  In addition, the calendar information generation unit 107 identifies a record corresponding to the identified record from the unique work definition information 750 (step S032). Specifically, the calendar information generation unit 107 specifies the record of the specific work definition information 750 in which the scheduled execution date and the work content of the record are stored as the common scheduled execution date field 751 and the work content field 754, respectively. Further, the calendar information generating unit 107 replaces the specified unique work definition information 750 record with the specified common work definition information 700 record.

  Further, the calendar information generation unit 107 acquires the date of the calendar day from a predetermined function unit (not shown) of the operator terminal 200 (step S033).

  Then, the calendar information generation unit 107 identifies the progress status of the work stored in the record including the date of the month for which the display request is received (step S034). Since the subsequent processing is the same as that in steps S023 to S025, description thereof is omitted.

  FIG. 16 is a diagram showing calendar information displayed after generation of the unique work definition information 750. As shown in the figure, in the calendar information generated based on the common work definition information 700, an icon indicating a common scheduled execution date displayed on March 10 is displayed on March 12. In addition, other common work is displayed as it is, since there is no change on the scheduled date of implementation.

  According to such a school lunch management apparatus, it is possible to more easily perform the work registered in association with the date of the calendar. In particular, school faculty and staff only need to change the scheduled date of common work that is performed every year according to the schedule of their school, so it is possible to improve the efficiency of such regular work registration . In addition, since only the difference between the common scheduled implementation date and the scheduled implementation date unique to the school is displayed as the school's own scheduled implementation date, a misleading display in which the icon is displayed even on the date when there is no planned implementation date Can be prevented.

  In the second embodiment described above, after changing the common scheduled execution date, the common scheduled execution date before the change was not displayed on the calendar. Both scheduled execution dates may be displayed. In this case, the calendar information generating unit 107 does not replace the record specified from the unique work definition information 750 with the corresponding record of the common work definition information 700, but adds it to the common work definition information 700. In this way, the icon is displayed on the common scheduled date, and the school-specific scheduled date (the scheduled date after the change) is also displayed on the calendar.

  Moreover, in a modification, you may make it display the icon displayed on a common scheduled implementation date, and the icon displayed on a scheduled implementation date peculiar to a school by a mutually different color. By the color coding, it is possible to easily identify whether the date is a common implementation date or a school-specific implementation date.

  In the second embodiment described above, the school terminal of each school displays the calendar information in which each school's own scheduled implementation date is displayed and the calendar information in which both the common scheduled implementation date and the school-specific implementation date are displayed. Although displayed in 300, in a modification, calendar information in which both the scheduled execution date related to the operator-specific work and the scheduled execution date of the common work are displayed may be displayed on the operator terminal 200. .

  In addition, the administrator terminal 200, according to the administrator authority of the system, displays calendar information on which each school's own scheduled execution date is displayed and calendar information on which both the common scheduled implementation date and the school-specific scheduled execution date are displayed. It may be displayed.

  In the first embodiment described above, it is assumed that an operator of the school board or a school staff member collectively registers the number of meals for a predetermined period (for example, one month of each month) in the meal number information 110. However, the present invention is not limited to such an embodiment. For example, a school staff member may perform the work of registering the number of meals of the day in the school lunch cost management system 1000 every day. Hereinafter, such a modification will be described.

  The server apparatus 100 according to the modification further includes a eating number management unit as a functional unit. The eating number management unit is a functional unit that manages the number of daily eatings. Specifically, the number-of-eats management unit accepts registration of school lunch dates from the faculty and staff via the school terminal 300. In addition, the eating number management unit accepts an input of the number of eating from the teacher through the school terminal 300. In addition, the number of meals management unit generates the number of meals management information storing the number of meals and the number of meals. In addition, the number of meals management unit specifies a date on which the number of meals is not registered, and displays a predetermined icon on the specified date via the output processing unit 104. .

  FIG. 17 is a diagram showing an example of the number of meals registration management information 900. The eating number registration management information 900 has a date column 901, a lunch implementation date flag column 902, and a lunch number registered flag column 903. The numerical information stored in the date column 901 is information for specifying the date of each month. The numerical information stored in the school lunch execution date flag column 902 is information that specifies whether or not it is the school lunch implementation date. For example, when “1” is stored in the school lunch implementation date flag column 902, it indicates that the school lunch is performed. In addition, when “0” is stored in this column, the day indicates a day on which no school lunch is performed. The numerical information stored in the number of registered meals flag field 903 is information that specifies whether or not registration of the number of meals has been accepted. For example, when “1” is stored in the number of meals registration flag field 903, it indicates that the registration of the number of meals corresponding to the date has been completed. Further, when “0” is stored in such a field, it indicates that the registration of the number of eating is not completed. Such meal number registration management information 900 is generated and updated by using the input information received from the school staff by the meal number management unit. The generated meal number registration management information 900 is stored in the storage unit 102.

  For example, the number-of-eats-feeding management section provides a menu item 600 shown in FIG. 8 with a registration item for the number of meals to be performed and a registered item for the number of meals, and receives selections from faculty members. Moreover, when the registration instruction | indication registration instruction | indication is received, the number of meal management part displays the lunch implementation date registration screen 910 shown to Fig.18 (a) on the school terminal 300, and receives the registration of the implementation date of a lunch. FIG. 18 is a diagram illustrating an example of a school lunch implementation date registration screen 910. The school faculty member, for example, selects the date on which the school lunch is conducted and presses the registration button 911 to register the school lunch implementation date in the school lunch cost management system 1000. Specifically, the number of meals management unit stores “1” in the lunch execution date flag column 902 corresponding to the date on which the selection is accepted (the date on which the icon with lunch is displayed), “0” is stored in the lunch execution date flag column 902 corresponding to the date on which the icon is displayed.

  In addition, the eating number management unit displays the eating number registration screen 920 shown in FIG. 18B on the school terminal 300, and accepts the number of eatings. FIG. 18B is a diagram showing an example of the number of eating registration screen 920. The school faculty member selects, for example, the date on which the school lunch was performed, inputs the actual number of meals that day, that is, the actual number of meals consumed, and presses the registration button 921, thereby pressing the number of meals. Is registered in the school lunch fee management system 1000. Specifically, the number of meals management unit stores “1” in the number of meals registration flag field 903 corresponding to the date when the number of meals is input, and the number of meals corresponding to the date when the number of meals is not input. “0” is stored in the registration flag column 904. The eating number management unit updates the eating number information 111 by associating the inputted number of eating with the eating person.

  In addition, when the number of meals management unit obtains an instruction to display calendar information via the input reception unit 103, the number of meals is determined to determine whether there is a date on which the number of meals is served and the number of meals is not registered. . Specifically, the eating number management unit determines whether or not there is a record in which “1” is stored in the lunch execution date flag column 902 and “0” is stored in the eating number registration flag column 903. If there is a record, the date is specified from the date column 901 of the record.

  In addition, the eating number management unit outputs an instruction to display a predetermined icon indicating that the number of eatings is not registered on the specified date to the output processing unit 104. FIG. 19B is a diagram illustrating an example of an icon indicating that the number of eating is not registered. Such an icon is assumed to be included in the icon information 500, for example.

  The output processing unit 104 causes the school terminal 300 to display calendar information displaying an icon indicating that the number of eating is not registered on the date specified by the number of eating management unit. In addition, when displaying the predetermined | prescribed icon which shows a work progress status on the date which the number-of-eats management part specified, the output process part 104 displays the calendar information which displayed these icons superimposed on this date to the school terminal 300. Display.

  FIG. 19A is a diagram illustrating an example of a screen example 930 on which calendar information generated according to this modification is displayed. In the calendar, an icon indicating the progress status of the work described in the above-described embodiment and an icon indicating that the number of meals has not been registered are displayed. For example, when the calendar day is March 26, an icon indicating unregistered is displayed on a date on which the number of meals before that date is not registered. In addition, an icon indicating unregistration is also displayed on March 29th, 30th, and 31st, which are dates earlier than the day of the calendar, which is the school lunch implementation date. By displaying such calendar information, forgetting to register the number of meals that require daily registration can be prevented.

  In the above-described modification, an icon indicating that the number of meals has not been registered is displayed on the date of school lunch, which is earlier than the date of the calendar day. You may make it display the icon which shows that the number of eating is unregistered for the date.

1000: Lunch cost management system as an example of work management system, 100: Server device as work management device (lunch cost management device), 200: Operator terminal, 300: School terminal, 101 ... Control part, 102 ... Storage part, 103 ... Input reception part,
104 ... output processing unit, 105 ... lunch cost calculation unit, 106 ... work definition information update unit,
107: Calendar information generation unit, 108: Notification document creation unit,
110 ... Destination information, 111 ... Number of meals, 112 ... Lunch cost information,
400 ... work definition information, 500 ... icon information, 120 ... communication unit,
201 ... Input unit, 202 ... Output unit, 203 ... Storage unit, 204 ... Communication unit,
301... Input information reception unit, 302... Output information processing unit, 303.
304: Information storage unit

Claims (13)

A control unit that executes predetermined processing; and a storage unit that stores predetermined information;
The storage unit
It has work definition information in which work contents related to a predetermined management work and scheduled work execution period are associated,
The controller is
Generate calendar information displaying a predetermined icon on the scheduled execution date of the work,
When receiving the selection of the icon, generates screen information for receiving an operation execution instruction with the date on which the selected icon is displayed as the scheduled execution date,
When the execution instruction is accepted, a predetermined process that can be executed by a computer corresponding to the work is executed. A school lunch management apparatus capable of performing predetermined processing relating to school lunch management work,
A control unit that executes predetermined processing; and a storage unit that stores predetermined information;
The storage unit
It has work definition information in which the work contents of the work related to the management of school lunch expenses and the scheduled execution period of the work are associated,
The controller is
Generate calendar information displaying a predetermined icon on the scheduled execution date of the work,
When receiving the selection of the icon, generates screen information for receiving an operation execution instruction with the date on which the selected icon is displayed as the scheduled execution date,
When the execution instruction is received, a predetermined process that can be executed by a computer according to the work is executed. A school lunch management apparatus according to claim 2,
The controller is
When there are a plurality of operations that have the date of selection received as the scheduled date of implementation, a predetermined processing according to the plurality of operations that can be performed by the computer is continuously executed. A school lunch management apparatus according to claim 2,
The controller is
A lunch expense management apparatus characterized by accepting registration of an execution scheduled date and an implementation deadline that are scheduled to be implemented in association with the work content. It is the lunch expense management apparatus as described in any one of Claims 2-4,
The controller is
Accepting the input of the work status indicating the work-in-progress status for each work,
A predetermined icon indicating the work state is specified according to a generation date of the calendar information, the scheduled execution period of the work, and the work state, and the icon is displayed on the calendar information. School lunch management device. A school lunch management apparatus according to claim 2,
The storage unit
Common work definition information that stores information related to the work that is common to each school, and unique information that stores information related to the work, including the scheduled work date unique to each school, that is different from the common scheduled work date. Work definition information,
The controller is
A school lunch expense management apparatus characterized in that a difference between the common scheduled implementation date and the scheduled implementation date specific to each school is obtained, and the scheduled implementation date unique to each school is specified. It is the lunch expenses management apparatus of Claim 6, Comprising: The said control part is
Generate the calendar information on which the predetermined icon is displayed on the scheduled implementation date of each school determined by the difference,
Based on the selection of the icon, accepting an execution instruction for the work with the date on which the icon is displayed as the scheduled date of execution,
Based on the acquisition of the execution instruction, a predetermined processing that can be executed by a computer according to the work is executed. It is the lunch expense management apparatus of Claim 6, Comprising:
The controller is
The school lunch cost management apparatus, wherein the predetermined icon is displayed on a scheduled execution date common to the schools and a scheduled schedule date unique to each school. It is the lunch expenses management device according to claim 8,
The controller is
The school lunch is characterized in that the display color of the icon displayed on the date scheduled for the implementation date common to each school and the icon displayed on the date scheduled for the implementation date specific to each school are different. Cost management device. It is the lunch expenses management device according to any one of claims 2 to 9,
The controller is
A school lunch cost management apparatus for generating screen information for displaying the calendar information on at least one of an operator who performs a school lunch management business and the school. A school lunch management apparatus according to claim 1,
The storage unit
It has lunch number registration management information that correlates information indicating the implementation date of lunch and the presence or absence of registration of the number of meals for each date,
The controller is
A school lunch cost management apparatus, characterized by specifying a date that is an implementation date of lunch and an unregistered number of meals, and generating calendar information with a predetermined icon displayed on the specified date. The computer is a school lunch management method for executing a predetermined process related to a school lunch management business,
The computer
Executing a control step for executing predetermined processing and a storage step for storing predetermined information;
In the storing step,
Stores work definition information in which work contents related to management of school lunch expenses and the scheduled execution period of work are associated,
In the control step,
Generating calendar information displaying a predetermined icon on the scheduled date of the work;
Receiving the selection of the icon, generating screen information for receiving an operation execution instruction with the date on which the selected icon is displayed as the scheduled implementation date;
When the execution instruction is received, a step of executing a predetermined process that can be executed by a computer according to the work is performed. A lunch cost management program for causing a computer to function as a lunch cost management apparatus capable of executing a predetermined process related to a lunch cost management operation,
The computer,
Function as a control unit that executes predetermined processing and a storage unit that stores predetermined information;
The storage unit
It has work definition information in which the work contents of the work related to the management of school lunch expenses and the scheduled execution period of the work are associated,
The controller is
Generate calendar information displaying a predetermined icon on the scheduled execution date of the work,
When the selection of the icon is received, screen information for receiving an operation execution instruction with the date on which the selected icon is displayed as the scheduled execution date is generated,
When the execution instruction is accepted, a predetermined process that can be executed by the computer according to the work is executed.

Images