Terminal device, business management system and program

Abstract

To prevent business that needs not be executed primarily from being executed.SOLUTION: A CPU 21 of a handy terminal 20 receives input of an ID (log-in information) of a person in charge, displays a business schedule that a user corresponding to the ID of a person in charge who receives the input should perform within a predetermined period on a display part 25, and starts a business application program used in business included in the business schedule. The CPU 21 also displays each business included in a business schedule in a selectable mode when displaying the business schedule, and starts a business application program corresponding to one business when operation for selecting the one business from the business schedule is performed.SELECTED DRAWING: Figure 21

Description

[Technical field]

[0001] The present invention relates to a terminal device, a business management system, and a program. [Background technology]

[0002] Conventionally, there has been known a sales management system that includes a handheld terminal used for tasks such as inventorying goods, outgoing inspection, and incoming inspection, and a PC (Personal Computer) that works in conjunction with the handheld terminal to manage information relating to each of the above tasks.

[0003] When using the above handheld terminal to perform a task, the user must select and input the task to be performed from the displayed menu, which may result in the user performing a task that is not actually required.Therefore, a technique has been disclosed that prevents the user from performing a task that is not actually required by displaying a menu that limits the tasks that can be selected and input according to the job type of the user using the handheld terminal (e.g., sales manager, sales representative 1, sales representative 2, etc.) (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2016-15176 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the technology disclosed in the above Patent Document 1, for example, if the user's job type is sales representative 1, the menu displayed is narrowed down to two options, "Orders" and "Sales." However, since "Orders" can be selected and input even on days when order-taking work does not need to be performed, there is still a problem in that work that does not actually need to be performed is performed.

[0006] The present invention has been made in consideration of such problems, and has an object to prevent tasks that do not need to be performed from being executed. [Means for solving the problem]

[0007] In order to solve the above problem, a terminal device according to the present invention comprises: A receiving means for receiving input of login information; a display control means for displaying, on a display unit, a work schedule to be performed within a predetermined period by a user corresponding to the login information input and accepted by the accepting means; a start control means for starting a business application program used in the business included in the business schedule; A first recording means for recording work processing information; A transmitting means for transmitting the work processing information recorded by the first recording means to a predetermined external device; Equipped with the display control means, when displaying the business schedule, displays each of the businesses included in the business schedule in a selectable manner; When an operation for selecting one task from the task schedule is performed, The startup control means Activating a business application program corresponding to the one business the display control means causes the display unit to display a work processing screen that accepts input of the work processing information related to the one job; the first recording means records the work processing information input on the work processing screen; the transmission means transmits the work processing information recorded by the first recording means to the predetermined external device in response to an operation of selecting a work completion button displayed in a selectable manner on the display unit by the display control means when any of the works included in the work schedule is completed; It is characterized by: Effect of the Invention

[0008] According to the present invention, it is possible to prevent a task that does not need to be performed from being executed. [Brief description of the drawings]

[0009] [Figure 1] 1 is a schematic configuration diagram of a sales management system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a block diagram showing the functional configuration of a PC. [Diagram 3] FIG. 13 is a diagram showing an example of the contents of a product master file. [Figure 4] FIG. 13 is a diagram showing an example of the contents of an order receipt file. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of an inventory master file. [Figure 6] FIG. 13 is a diagram showing an example of the contents of an HT task list file. [Figure 7] FIG. 2 is a block diagram showing a functional configuration of the handheld terminal. [Figure 8] 13 is a flowchart showing a control procedure for a business schedule creation process. [Figure 9] FIG. 13 is a diagram illustrating an example of a business schedule creation screen. [Figure 10] 13 is a flowchart showing a control procedure for a task extraction process. [Figure 11] FIG. 4 is a diagram showing an example of the contents of work schedule data. [Figure 12] FIG. 13 is a diagram showing an example of the contents of shipping inspection instruction data. [Figure 13] FIG. 13 is a diagram showing an example of the contents of inventory instruction data. [Figure 14] 13 is a flowchart showing a control procedure of a detailed setting process. [Figure 15] FIG. 13 is a diagram showing an example of a detailed setting screen. [Figure 16] FIG. 4 is a diagram showing an example of the contents of work schedule data. [Figure 17] 13 is a flowchart showing a control procedure of an HT task execution control process. [Figure 18] FIG. 13 is a diagram illustrating an example of a business login screen. [Figure 19] FIG. 13 is a diagram showing an example of a business menu screen. [Figure 20] 13 is a flowchart showing a control procedure for a business schedule display process. [Figure 21] FIG. 13 is a diagram illustrating an example of a business schedule screen. [Figure 22] 13 is a flowchart showing a control procedure for a business application execution process. [Diagram 23] FIG. 13 is a diagram showing an example of a work processing screen. [Figure 24]FIG. 13 is a diagram showing an example of a work processing screen. [Diagram 25] FIG. 13 is a diagram showing an example of the contents of a business schedule execution log file. [Figure 26] 13 is a flowchart showing a control procedure of a result import process. [Figure 27] 13 is a flowchart showing a control procedure for a business schedule execution log display process. [Figure 28] FIG. 13 is a diagram showing an example of a business schedule execution log display acceptance screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings, however, the scope of the present invention is not limited to the illustrated examples.

[0011] <Sales management system configuration> First, the configuration of this embodiment will be described with reference to Fig. 1. Fig. 1 is a schematic diagram of a sales management system (business management system) 100 of this embodiment.

[0012] 1, the sales management system 100 includes a PC 10 as a management device and a handheld terminal 20 as a terminal device. The PC 10 and the handheld terminal 20 are connected to be able to communicate information via a communication network N. The number of handheld terminals 20 is not limited to one, and may be multiple.

[0013] The PC 10 is a device for managing information related to operations such as inventory, shipping inspection, and receiving inspection of products, which are carried out using the handheld terminal 20. The PC 10 is a device used, for example, by an employee (hereinafter referred to as the "manager") who is in a position to supervise part-time employees who use the handheld terminal 20 in a company that has introduced the sales management system 100.

[0014] The handy terminal 20 is a device that is carried out to the site by part-time employees or the like and accepts input of information related to work. The handy terminal 20 is assumed to be commonly used among a plurality of part-time employees.

[0015] The communication network N is assumed to be, for example, the Internet, but may be another network such as a LAN (Local Area Network).

[0016] <Configuration of PC> Next, with reference to FIG. 2, the functional configuration of the PC 10 will be described. FIG. 2 is a block diagram showing the functional configuration of the PC 10.

[0017] As shown in FIG. 2, the PC 10 includes a CPU (Central Processing Unit) 11, a RAM (Random Access Memory) 12, a storage unit 13, an operation unit 14, a display unit 15, a communication unit 16, a timing unit 17, and a bus 18. Each part of the PC 10 is connected via the bus 18.

[0018] The CPU 11 is a processor that controls each part of the PC 10. The CPU 11 reads out a specified program from the system program and application programs stored in the storage unit 13, expands it in the RAM 12, and executes various processes according to the program.

[0019] The RAM 12 is, for example, a volatile memory and has a work area for temporarily storing various programs and data read by the CPU 11.

[0020] The storage unit 13 includes a storage device capable of writing and reading data, such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive), and stores various programs and data. Data stored in the storage unit 13 includes a product master file 131, an order slip file 132, an inventory master file 133, an HT (handy terminal) work list file 134, and the like.

[0021] The storage unit 13 is also provided with a person-specific folder 135 and a person-specific import folder 136 . The individual folders 135 are folders assigned to each part-time employee who is in charge of work using the handheld terminal 20, and the work schedule data (described later) and work data (described later) of the part-time employee corresponding to each folder are registered therein. The person-specific import folder 136, like the person-specific folder 135, is a folder assigned to each part-time employee, and after the work using the handheld terminal 20 is completed, the work schedule data (described later), work data (described later), and work schedule execution log file (described later) uploaded from the handheld terminal 20 are registered in the folder of the part-time employee (person in charge) who was in charge of the work.

[0022] FIG. 3 is a diagram showing an example of the contents of the product master file 131. As shown in FIG. The product master file 131 is a file that stores information about products handled in various business operations, and as shown in FIG. 3, for each product, information such as the product code, product name, unit name, standard unit price, etc. is stored in correspondence with each other.

[0023] FIG. 4 is a diagram showing an example of the contents of the order slip file 132. The order slip file 132 is a file that stores information on order slips that are created when a product order is received from a customer. As shown in FIG. 4, for each ordered product, information such as the slip number, slip date, scheduled shipping date, customer code, customer name, product code, product name, quantity, etc. is stored in correspondence with each other.

[0024] FIG. 5 is a diagram showing an example of the contents of the inventory master file 133. The inventory master file 133 is a file that stores information necessary for inventory management of each product stored in the product master file 131. As shown in FIG. 5, information such as the product code, product name, stock quantity, and planned inventory date is stored in association with each product.

[0025] FIG. 6 is a diagram showing an example of the contents of the HT task list file 134. As shown in FIG. The HT task list file 134 is a file that defines tasks to be performed using the handheld terminal 20, and as shown in Fig. 6, each piece of information such as the HT task name, program name, extraction conditions, etc. is stored in association with each task. The program name is the name of the task application program that is started in the handheld terminal 20 when performing the task. The extraction conditions are the conditions when task data (described later) used as work instruction information for a person in charge when performing a task using the handheld terminal 20 is extracted from a specified file.

[0026] The operation unit 14 has a key input unit such as a keyboard and a pointing device such as a mouse, and accepts key operation input and position operation input from the user and outputs the operation information to the CPU 11. The CPU 11 accepts the user's input operation based on the information transmitted from the operation unit 14.

[0027] The display unit 15 is configured with an LCD (Liquid Crystal Display), an EL (Electro Luminescence) display, or the like, and performs various displays according to display information instructed by the CPU 11.

[0028] The communication unit 16 is configured by a network card etc. The communication unit 16 is communicatively connected to a communication network N and communicates with devices on the communication network N.

[0029] The clock unit 17 is configured with an RTC (Real Time Clock) or the like, and obtains the current date and time and outputs it to the CPU 11.

[0030] <Handheld terminal configuration> Next, the functional configuration of the handy terminal 20 will be described with reference to Fig. 7. Fig. 7 is a block diagram showing the functional configuration of the handy terminal 20.

[0031] 7, the handheld terminal 20 includes a CPU 21, a RAM 22, a storage unit 23, an operation unit 24, a display unit 25, a communication unit 26, a scanner unit 27, a clock unit 28, and a bus 29. The various units of the handheld terminal 20 are connected to each other via the bus 29.

[0032] The CPU 21 (accepting means, display control means, start control means, acquiring means, first recording means, transmitting means, second recording means) is a processor that controls each part of the handheld terminal 20. The CPU 21 reads out a specified program from among the system programs and application programs stored in the storage unit 23, expands it in the RAM 22, and executes various processes according to the program.

[0033] The RAM 22 is, for example, a volatile memory, and has a work area for temporarily storing various programs and data read by the CPU 21.

[0034] The storage unit 23 is a non-volatile storage unit such as a flash memory to which data can be written and read, and stores various programs, data, and the like.

[0035] The operation unit 24 includes a keypad that accepts operation input from various keys, and outputs operation information according to the key operation input to the CPU 21. The various keys of the operation unit 24 include numeric and character input keys, various function keys, a trigger key for executing a scan by the scanner unit 27, and the like.

[0036] The display unit 25 is composed of an LCD, an EL display, or the like, and performs various displays according to display information instructed by the CPU 21.

[0037] The communication unit 26 is at least one wireless communication unit having antennas, modulation / demodulation circuits, signal processing circuits, etc. for various wireless communication methods, and performing wireless communication with a communication destination. The wireless communication method of the communication unit 26 is a wireless LAN such as Wi-Fi (registered trademark), a wireless WAN (Wide Area Network), NFC (Near Field Communication), etc. For example, the CPU 21 performs wireless transmission and reception with an access point by Wi-fi communication via the communication unit 26, and transmits and receives information to and from a communication destination device network-connected to the access point.

[0038] Scanner unit 27, under the control of CPU 21, captures an image of a symbol (e.g., a one-dimensional barcode, a two-dimensional barcode, etc.) as a subject, generates image data thereof, and outputs the image data to CPU 21. CPU 21 decodes the image data of the symbol captured by scanner unit 27, and acquires code information contained in the symbol.

[0039] The clock unit 28 is configured with an RTC or the like, and obtains the current date and time and outputs it to the CPU 21.

[0040] Next, a series of operations related to the management of business using the handy terminal 20 performed by the sales management system 100 will be described with reference to FIGS.

[0041] <Business schedule creation process> First, the work schedule creation process performed by the PC 10 will be described with reference to Fig. 8. This work schedule creation process is a process in which a manager creates a work schedule as work instructions for each part-time employee on the PC 10 before the start of work for the day. Fig. 8 is a flowchart showing the control procedure of the work schedule creation process. The work schedule creation process is started, for example, when a menu button corresponding to the "Work Schedule Creation" item on a menu screen (not shown) is selected via the operation unit 14.

[0042] As shown in FIG. 8, when the business schedule creation process is started, the CPU 11 of the PC 10 first causes the display unit 15 to display a business schedule creation screen 41 (step S1).

[0043] FIG. 9 is a diagram showing an example of a business schedule creation screen 41. As shown in FIG. 9, work schedule creation screen 41 is provided with a text box 411, and CPU 11 accepts input of the name of a part-time employee (person in charge) for whom a work schedule is to be created in this text box 411 (step S2). Note that text box 411 may allow the manager to select and input the name of a desired part-time employee using, for example, a pull-down menu.

[0044] Next, the CPU 11 executes a task extraction process (step S3).

[0045] FIG. 10 is a flowchart showing a control procedure for the task extraction process. As shown in FIG. 10, when the assigned task extraction process is started, the CPU 11 first reads out the HT task list file 134 from the storage unit 13 (step S11).

[0046] Next, the CPU 11 assigns 1 to a variable n (step S12). The variable n is a variable for designating a record line of the HT task list file 134 (see FIG. 6).

[0047] Next, the CPU 11 acquires the extraction condition of the record in the first (N=1) line, that is, the extraction condition related to the shipping inspection work, "order slip: scheduled shipping date=today" (step S13).

[0048] Next, CPU 11 searches for data using the extraction condition acquired in step S13 (step S14). Specifically, when the extraction condition is "order slip: scheduled shipping date = today", CPU 11 searches order slip file 132 (see FIG. 4) for data in which the scheduled shipping date is set to today. Also, when the extraction condition is "inventory master: scheduled inventory date = today", CPU 11 searches inventory master file 133 (see FIG. 5) for data in which the scheduled inventory date is set to today.

[0049] Next, the CPU 11 determines whether or not there is corresponding data based on the search result in step S14 (step S15).

[0050] If it is determined in step S15 that there is relevant data (step S15; YES), the CPU 11 creates work schedule data Da1 for the part-time employee (e.g., Taro Sato) whose name was entered in the text box 411 on the work schedule creation screen 41 (step S16). For example, if it is determined that there is relevant data for the records on the first and second lines of the HT work list file 134, i.e., the shipping inspection work and the inventory work, the CPU 11 creates work schedule data Da1 based on the data of the records on the first and second lines. The created work schedule data Da1 is temporarily stored in the RAM 12.

[0051] FIG. 11 is a diagram showing an example of the content of the work schedule data Da1. The work schedule data Da1 is data that records information required to display a work schedule (see FIG. 21) on the display unit 25 when a work is performed using the handheld terminal 20, and as shown in FIG. 11, for each work to be performed, information on the person in charge, work name, start time (scheduled start time), end time (scheduled end time), startup program, and work data is stored in association with each other. Here, information on the work data items indicates the work data linked to the corresponding work.

[0052] Next, the CPU 11 creates business data (step S17). For example, if it is determined that there is relevant data for the record on the first line of the HT business list file 134, i.e., the shipping inspection business, the CPU 11 creates shipping inspection instruction data Db1, which is business data, based on the relevant data in the order receipt file 132. Also, for example, if it is determined that there is relevant data for the record on the second line of the HT business list file 134, i.e., the inventory business, the CPU 11 creates inventory instruction data Db2, which is business data, based on the relevant data in the inventory master file 133. The created business data is temporarily stored in the RAM 12.

[0053] FIG. 12 is a diagram showing an example of the contents of the shipping inspection instruction data Db1. The shipping inspection instruction data Db1 is data that records information required for displaying work instruction information for a person in charge on the display unit 25 when the shipping inspection work is performed using the handheld terminal 20, and as shown in Fig. 12, for each item subject to shipping inspection, information on the person in charge, slip number, customer code, customer name, product code, product name, and quantity is stored in association with each other. Also, the shipping inspection instruction data Db1 has an item for inspection quantity, and is capable of recording the inspection quantity (actual result) input from the handheld terminal 20 when the shipping inspection work is actually performed.

[0054] FIG. 13 is a diagram showing an example of the contents of the inventory instruction data Db2. The inventory instruction data Db2 is data that records information required for displaying work instruction information for a person in charge on the display unit 25 when inventory work is performed using the handheld terminal 20, and as shown in Fig. 13, the person in charge, product code, product name, and planned quantity are stored in association with each other for each item to be inventoryed. In addition, the inventory instruction data Db2 has an item for inventory quantity, and is capable of recording the inventory quantity (actual result) input from the handheld terminal 20 when an actual inventory work is performed.

[0055] Moreover, in step S15, if it is determined that there is no corresponding data (step S15; NO), the CPU 11 skips steps S16 and S17 and advances the process to step S18.

[0056] Next, the CPU 11 judges whether or not there is a record in the 2(N+1)th line in the HT task list file 134 (step S18).

[0057] In step S18, if it is determined that the HT task list file 134 has a record on the 2(N+1)th line (step S18; YES), the CPU 11 increments the variable n by 1 (step S19). Then, the CPU 11 returns the process to step S13 and repeats the subsequent processes. On the other hand, in step S18, if it is determined that there is no record in the 2(N+1)th line in the HT task list file 134 (step S18; NO), the CPU 11 ends the responsible task extraction process and returns the process to the task schedule creation process.

[0058] Returning to the business schedule creation process (see FIG. 8), the CPU 11 displays a list of responsible tasks on the business schedule creation screen 41 (step S4). Here, the tasks listed in the list of responsible tasks are tasks (e.g., shipping inspection and inventory) for which the business schedule data Da1 and business data (e.g., shipping inspection instruction data Db1, inventory instruction data Db2, etc.) have been created in the responsible task extraction process described above and are temporarily stored in the RAM 12.

[0059] Next, the CPU 11 determines whether or not the end button 414 provided on the business schedule creation screen 41 has been pressed (step S5).

[0060] In step S5, when it is determined that the end button 414 has been pressed (step S5; YES), the CPU 11 ends the business schedule creation process. On the other hand, when it is determined in step S5 that the end button 414 has not been pressed (step S5; NO), the CPU 11 determines whether or not the detail setting button 412 provided on the work schedule creation screen 41 has been pressed (step S6). The detail setting button 412 is provided in association with each of the tasks listed in the list of tasks, as shown in Fig. 9. That is, in the example of Fig. 9, two detail setting buttons are provided: a detail setting button 412 for the shipping inspection task and a detail setting button 412 for the inventory task.

[0061] If it is determined in step S6 that the detailed setting button 412 has not been pressed (step S6; NO), the CPU 11 skips step S7 and advances the process to step S8. On the other hand, if it is determined in step S6 that the detail setting button 412 has been pressed (step S6; YES), the CPU 11 executes a detail setting process (step S7).

[0062] FIG. 14 is a flowchart showing a control procedure of the detailed setting process. As shown in FIG. 14, when the detail setting process is started, the CPU 11 first causes the display unit 15 to display the detail setting screen 42 (step S21).

[0063] FIG. 15 is a diagram showing an example of a detailed setting screen 42 relating to the shipping inspection work. 15, the detailed setting screen 42 displays the word "shipping inspection" as the name of the task for which detailed settings are to be made. Also, below the word "shipping inspection" on the detailed setting screen 42, a text box 421 for inputting the start time (scheduled start time) of the shipping inspection task and a text box 422 for inputting the end time (scheduled end time) are provided. In this example of the detailed setting screen 42, a state in which "13:00" has been inputted into the text box 421 and "15:00" has been inputted into the text box 422 is shown.

[0064] Furthermore, the detailed setting screen 42 has a text box 423 for inputting extraction conditions below the above text boxes 421, 422. The extraction conditions set in the HT task list file 134 (see FIG. 6) are input by default in this text box 423. In this example of the detailed setting screen 42, the extraction condition "order slip: scheduled shipping date = today" set in the HT task list file 134 is shown input in the text box 423, and the relevant data in the order slip file 132 searched for with this extraction condition is displayed.

[0065] Next, the CPU 11 accepts an input of the start time (scheduled start time) of the target task in the text box 421, and accepts an input of the end time (scheduled end time) in the text box 422 (step S22).

[0066] Next, the CPU 11 determines whether or not the extraction conditions have been changed in the text box 423 (step S23).

[0067] If it is determined in step S23 that the extraction conditions have been changed (step S23; YES), CPU 11 searches for data using the changed extraction conditions (step S24). For example, if the extraction conditions are changed from "order slip: scheduled shipping date = today" to "order slip: scheduled shipping date = today afternoon", data for which the scheduled shipping date is set to today afternoon is searched for from order slip file 132 (see FIG. 4).

[0068] Next, CPU 11 displays the search results below text box 423 (step S25). Specifically, if the search results include data that meets the changed extraction conditions, CPU 11 displays the data. On the other hand, if the search results include no data that meets the changed extraction conditions, CPU 11 displays a message indicating that there is no applicable data.

[0069] Moreover, in step S23, if it is determined that the extraction conditions have not been changed (step S23; NO), the CPU 11 skips steps S24 and S25 and advances the process to step S26.

[0070] Next, the CPU 11 determines whether or not the OK button 424 has been pressed on the detailed setting screen 42 (step S26).

[0071] In step S26, if it is determined that the OK button 424 has not been pressed (step S26; NO), the CPU 11 returns the process to step S22 and repeats the subsequent processes. On the other hand, if it is determined in step S26 that the OK button 424 has been pressed (step S26; YES), the CPU 11 updates the business schedule data Da1 and business data (e.g., shipping inspection instruction data Db1, inventory instruction data Db2, etc.) based on the data entered and displayed on the detailed setting screen 42 at this time (step S27), and returns the process to the business schedule creation process.

[0072] For example, when a start time of "13:00" and an end time of "15:00" are entered in text boxes 421, 422 on the detailed setting screen 42 for the shipping inspection work and the OK button 424 is pressed, and when a start time of "15:00" and an end time of "17:00" are entered in text boxes 421, 422 on the detailed setting screen 42 for the inventory work (not shown), the business schedule data Da1 is updated to include the start times and end times of the shipping inspection work and the inventory work, as shown in FIG. 16.

[0073] Returning to the business schedule creation process (see FIG. 8), the CPU 11 determines whether or not the registration button 413 provided on the business schedule creation screen 41 has been pressed (step S8).

[0074] In step S8, if it is determined that the registration button 413 has not been pressed (step S8; NO), the CPU 11 returns the process to step S5 and repeats the subsequent processes. On the other hand, in step S8, if it is determined that the registration button 413 has been pressed (step S8; YES), the CPU 11 registers the business schedule data Da1 and business data (for example, shipping inspection instruction data Db1, inventory taking instruction data Db2, etc.) temporarily stored in the RAM 12 in the folder 135 for each person in charge (step S9). For example, when the business schedule data Da1 and business data (for example, shipping inspection instruction data Db1, inventory taking instruction data Db2, etc.) for Mr. Taro Sato, who is a part-time employee, are created, the CPU 11 registers these data in the folder for Mr. Taro Sato (folder 135 for each person in charge). Then, the CPU 11 returns the process to step S5 and repeats the subsequent processes.

[0075] <HT Business Execution Control Process> Next, referring to FIG. 17, the HT (handy terminal) business execution control process performed by the handy terminal 20 will be described. FIG. 17 is a flowchart showing the control procedure of the HT business execution control process. The HT business execution control process is started, for example, triggered by the operation of the power key (operation unit 24) and the startup of the handy terminal 20.

[0076] As shown in FIG. 17, when the HT business execution control process is started, the CPU 21 of the handy terminal 20 first causes the display unit 25 to display the business login screen 51 (step S31).

[0077] FIG. 18 is a diagram showing an example of the business login screen 51. As shown in Fig. 18, the business login screen 51 is provided with a person in charge input area 511 for inputting a person in charge ID (login information) of a person in charge as a login user. The CPU 21 accepts input of the person in charge ID in this person in charge input area 511 (step S32). The business login screen 51 shown in Fig. 18 shows a state in which a person in charge ID "1" is input in the person in charge input area 511 via the operation unit 24, and the person in charge "Taro Sato" corresponding to this person in charge ID "1" is displayed.

[0078] Next, CPU 21 downloads (acquires) data for the person in charge who is the logged-in user from person-specific folder 135 of PC 10 via communication unit 26 (step S33). For example, if the logged-in user is Taro Sato, CPU 21 downloads data from the folder for Taro Sato of PC 10 (person-specific folder 135).

[0079] Next, the CPU 21 determines whether or not the data downloaded in step S33 includes the target work schedule data Da1, that is, the work schedule data Da1 related to the work to be performed today (step S34).

[0080] In step S34, if it is determined that the target business schedule data Da1 is present (step S34; YES), the CPU 21 causes the display unit 25 to display the business menu screen 52 with the business schedule button 521 added to the top (step S35).

[0081] FIG. 19 is a diagram showing an example of the business menu screen 52 with a business schedule button 521 added to the top. 19, the business menu screen 52 is provided with, from the top, a business schedule button 521, a product management button 522, and an internet search button 523 as menu buttons. The business schedule button 521 is a button for displaying the business schedule on the display unit 25. The product management button 522 is a button for starting product management. The internet search button 523 is a button for starting an internet search. In addition, an exit button 524 for closing the business menu screen 52 is provided at the bottom right of the business menu screen 52.

[0082] When the task menu screen 52 with the task schedule button 521 added is displayed on the display unit 25, the buttons not directly related to the task, such as the Internet search button 523 on the menu screen 52, may be controlled so that they cannot be operated after the start of the task displayed on the task schedule screen 53 described below or during the task hours. This improves the work efficiency by preventing part-time employees from performing tasks not related to the task after the start of the task or during the task hours, and also prevents the leakage of business data by preventing them from accessing sites where security is not guaranteed.

[0083] Furthermore, in step S34, if it is determined that there is no target business schedule data Da1 (step S34; NO), the CPU 21 displays a normal business menu screen (not shown) on the display unit 25 (step S36). The normal business menu screen does not have the above-mentioned business schedule button 521 as a menu button, and only has two buttons, a product management button and an internet search button.

[0084] Next, the CPU 21 determines whether or not a menu button has been designated on the operation menu screen (for example, the operation menu screen 52) (step S37).

[0085] If it is determined in step S37 that a menu button designation operation has been performed (step S37; YES), the CPU 21 determines whether the menu button designated by the designation operation is the business schedule button 521 (step S38).

[0086] In step S38, when it is determined that the menu button designated is the business schedule button 521 (step S38; YES), the CPU 21 executes a business schedule display process (step S39) and advances the process to step S41. The business schedule display process will be described in detail later. On the other hand, if it is determined in step S38 that the menu button on which the specified operation was performed is not the business schedule button 521 (step S38; NO), the CPU 21 executes the business process corresponding to the menu button on which the specified operation was performed (the product management button or the Internet search button) (step S40), and proceeds to the process in step S41.

[0087] Moreover, in step S37, if it is determined that the menu button has not been specified (step S37; NO), the CPU 21 skips steps S38 to S39 and advances the process to step S41.

[0088] Next, the CPU 21 determines whether or not the end button 524 has been specified on the operation menu screen (step S41).

[0089] In step S41, when it is determined that the end button 524 has been specified (step S41; YES), the CPU 21 closes the task menu screen and ends the HT task execution control process. On the other hand, in step S41, if it is determined that the end button 524 has not been specified (step S41; NO), the CPU 21 returns the process to step S37 and repeats the subsequent processes.

[0090] Next, the business schedule display process will be described with reference to Fig. 20. Fig. 20 is a flowchart showing the control procedure of the business schedule display process.

[0091] As shown in FIG. 20, when the business schedule display process is started, the CPU 21 first causes the display unit 25 to display the business schedule screen 53 based on the business schedule data Da1 downloaded from the PC 10 (step S51).

[0092] FIG. 21 is a diagram showing an example of the business schedule screen 53. As shown in FIG. As shown in FIG. 21, the business schedule screen 53 is provided with a shipping inspection button 531 and an inventory button 532 as business buttons on which business to be performed is described. Here, the business to be performed is based on the information "shipping inspection" and "inventory" recorded in the business name item of the business schedule data Da1 (see FIG. 16) downloaded from the PC 10. In addition, above the shipping inspection button 531, "13:00" is displayed as the start time (scheduled start time) of the shipping inspection business, and "15:00" is displayed as the end time (scheduled end time). In addition, above the inventory button 532, "15:00" is displayed as the start time (scheduled start time) of the inventory business, and "17:00" is displayed as the end time (scheduled end time). The start time and end time of these businesses are based on the information recorded in the start time and end time items of the business schedule data Da1 (see FIG. 16) downloaded from the PC 10.

[0093] Further, a back button 533 and an end button 534 are provided at the bottom of the business schedule screen 53. The back button 533 is a button for closing the business schedule screen 53. The end button 534 is a button for uploading the business data and business schedule data Da1 in which the results (described later) of each business are registered and the business schedule execution log file 231 (described later) to the person-by-person import folder 136 of the PC 10 after each business is completed. Therefore, until each business is completed, the end button 534 is displayed in an inoperable state (for example, in a grayed-out state), and when each business is completed, the end button 534 is displayed in an operable state. Note that the end button 534 may be hidden until each business is completed, and displayed when each business is completed.

[0094] Next, the CPU 21 determines whether or not a task button (for example, the shipping inspection button 531, the inventory button 532; see FIG. 21) has been designated (step S52).

[0095] In step S52, when it is determined that the operation of specifying the business button has been performed (step S52; YES), the CPU 21 executes a business application execution process (step S53), and advances the process to step S54. The business application execution process will be described in detail later. On the other hand, if it is determined in step S52 that the operation of specifying the service button has not been performed (step S52; NO), the CPU 21 skips step S53 and advances the process to step S54.

[0096] Next, the CPU 21 determines whether or not the end button 534 has been specified (step S54).

[0097] If it is determined in step S54 that the end button 534 has been selected (step S54; YES), the CPU 21 uploads the business data and business schedule data Da1 in which the results of each business task (described later) are registered, and the business schedule execution log file 231 (described later) to the person-specific import folder 136 of the PC 10 via the communication unit 26 (step S55), and proceeds to the process of step S56. On the other hand, if it is determined in step S54 that the end button 534 has not been specified (step S54; NO), the CPU 21 determines whether or not the return button 533 has been specified (step S56).

[0098] In step S56, if it is determined that the back button 533 has been specified (step S56; YES), the CPU 21 closes the business schedule screen 53, and returns the process to the HT business execution control process (see FIG. 17). On the other hand, in step S56, if it is determined that the back button 533 has not been specified (step S56; NO), the CPU 21 returns the process to step S52 and repeats the subsequent processes.

[0099] Next, the business application execution process will be described with reference to Fig. 22. Fig. 22 is a flowchart showing the control procedure of the business application execution process.

[0100] As shown in Fig. 22, when the business application execution process is started, the CPU 21 first launches a business application program for a business corresponding to the business button designated on the business schedule screen 53 (see Fig. 21) (step S61). For example, when the shipping inspection button 531 is designated on the business schedule screen 53, a business application program related to the shipping inspection business is launched. Here, as the business application program related to the shipping inspection business, "Prog1.exe" recorded in the startup program item of the business schedule data Da1 (see Fig. 16) downloaded from the PC 10 is used.

[0101] Next, CPU 21 records the execution start time of one task (e.g., inspection work for product 1) in the corresponding task (e.g., shipping inspection task) in task schedule execution log file 231 (step S62). Here, each task of the corresponding task is a task based on data (task instruction information) recorded in the records of each line of the task data downloaded from PC 10. More specifically, each task of the shipping inspection task is a task based on data recorded in the records of the first to fourth lines of shipping inspection instruction data Db1 (see FIG. 12) downloaded from PC 10. Also, each task of the inventory task is a task based on data recorded in the records of the first to third lines of inventory instruction data Db2 (see FIG. 13) downloaded from PC 10.

[0102] FIG. 25 is a diagram showing an example of the contents of the business schedule execution log file 231. As shown in FIG. The business schedule execution log file 231 is a file for recording the start time and end time of an actually performed task for each task, and has items such as person in charge, task name, start time, and end time, as shown in Fig. 25. In the example of Fig. 25, it is recorded that the first task of shipping inspection by Taro Sato started at 13:10 and ended at 13:20. It is also recorded that the second task of shipping inspection by Taro Sato started at 13:30 and ended at 13:35. It is assumed that the business schedule execution log file 231 is stored in the memory unit 23.

[0103] Next, the CPU 21 determines whether there is any other unprocessed work in the corresponding work based on the business data (eg, the shipping inspection instruction data Db1, the inventory instruction data Db2, etc.) downloaded from the PC 10 (step S63).

[0104] In step S63, if it is determined that there is another unprocessed task (step S63; YES), the CPU 21 causes the display unit 25 to display a task processing screen 54 having a next button 543 based on the business data downloaded from the PC 10 (step S64).

[0105] FIG. 23 is a diagram showing an example of the work processing screen 54 on which a next button 543 is provided. 23, the work processing screen 54 is a screen generated based on the data (work instruction information) in the first line of the shipment inspection instruction data Db1 (see FIG. 12) downloaded from the PC 10. The work processing screen 54 is provided with a result display area 541 that displays the inspection quantity (results) in real time. When the person in charge inspects the target product (product 1), for example, each time the scanner unit 27 reads the symbol of the target product, the inspection quantity shown in the result display area 541 is counted up.

[0106] Next, the CPU 21 determines whether or not a designation operation of the registration button 542 provided on the work processing screen 54 has been performed (step S65).

[0107] In step S65, when it is determined that the registration button 542 has not been specified (step S65; NO), the CPU 21 repeats the determination process of step S65 until the registration button 542 is specified. On the other hand, in step S65, if it is determined that the registration button 542 has been selected (step S65; YES), the CPU 21 registers the actual result (inspection quantity) displayed in the result display area 541 in the inspection quantity item of the shipping inspection instruction data Db1 (see FIG. 12) (step S66).

[0108] Next, the CPU 21 determines whether or not a designation operation of the next button 543 provided on the job processing screen 54 has been performed (step S67).

[0109] In step S67, when it is determined that the next button 543 has not been specified (step S67; NO), the CPU 21 repeats the determination process of step S67 until the next button 543 is specified. On the other hand, if it is determined in step S67 that the Next button 543 has been selected (step S67; YES), the CPU 21 records the end time of the ongoing work (inspection work for product 1) in the business schedule execution log file 231 (step S68).

[0110] Next, the CPU 21 records the start time of the next task (inspection task of product 3) in the task schedule execution log file 231 (step S69). Then, the CPU 21 returns the process to step S63, and repeats the subsequent processes.

[0111] Furthermore, if it is determined in step S63 that there is no other unprocessed work (step S63; NO), the CPU 21 causes the display unit 25 to display a work processing screen 55 having an end button 553 based on the business data downloaded from the PC 10 (step S70).

[0112] FIG. 24 is a diagram showing an example of a work processing screen 55 on which an end button 553 is provided. 24, the work processing screen 55 is a screen generated based on the data (work instruction information) in the fourth line of the shipping inspection instruction data Db1 (see FIG. 12) downloaded from the PC 10. The work processing screen 55 is provided with a performance display area 551, similar to the work processing screen 54 described above.

[0113] Next, the CPU 21 determines whether or not a designation operation of the registration button 552 provided on the work processing screen 55 has been performed (step S71).

[0114] In step S71, when it is determined that the registration button 552 has not been specified (step S71; NO), the CPU 21 repeats the determination process of step S71 until the registration button 552 is specified. On the other hand, in step S71, if it is determined that the registration button 552 has been selected (step S71; YES), the CPU 21 registers the actual result (inspection quantity) displayed in the actual result display area 551 in the inspection quantity item of the shipping inspection instruction data Db1 (see FIG. 12) (step S72).

[0115] Next, the CPU 21 determines whether or not the end button 553 provided on the work processing screen 55 has been designated (step S73).

[0116] In step S73, when it is determined that the end button 553 has not been operated (step S73; NO), the CPU 21 repeats the determination process of step S73 until the end button 553 is operated. On the other hand, if it is determined in step S73 that the end button 553 has been selected (step S73; YES), the CPU 21 records the end time of the ongoing work (inspection work of product 8) in the business schedule execution log file 231 (step S74), and returns the process to the business schedule display process (see FIG. 20).

[0117] <Actual results import process> Next, the result import process performed by the PC 10 will be described with reference to Fig. 26. This result import process is a process in which the PC 10 transmits, after the end of a day's work, work data in which results are registered and uploaded from the handheld terminals 20 operated by each part-time employee to a specified external server (external device). Fig. 26 is a flowchart showing the control procedure of the result import process. The result import process is started, for example, when a menu button corresponding to the "Result Import" item on a menu screen (not shown) is selected via the operation unit 14.

[0118] As shown in FIG. 26, when the result import process is started, the CPU 11 of the PC 10 first causes the display unit 15 to display a result import acceptance screen (not shown) (step S81).

[0119] Next, the CPU 11 accepts input of the name of the part-time employee (person in charge) whose results are to be imported in a text box (not shown) provided on the results import acceptance screen (step S82).

[0120] Next, the CPU 11 determines whether or not an execution button (not shown) provided on the result import reception screen has been pressed (step S83).

[0121] In step S83, if it is determined that the execution button has not been pressed (step S83; NO), the CPU 11 skips steps S84 and S85 and advances the process to step S86. On the other hand, if it is determined in step S83 that the execute button has been pressed (step S83; YES), the CPU 11 reads out the business data of the target part-time employee (person in charge) from the person-by-person import folder 136 (step S84).

[0122] Next, the CPU 11 transmits the business data read out in step S84 to a predetermined external server (external device) via the communication unit 16 (step S85).

[0123] Next, the CPU 11 determines whether or not an end button (not shown) provided on the result import reception screen has been pressed (step S86).

[0124] In step S86, when it is determined that the end button has been pressed (step S86; YES), the CPU 11 ends the result import process. On the other hand, if it is determined in step S86 that the end button has not been pressed (step S86; NO), the CPU 11 returns the process to step S82 and repeats the subsequent processes.

[0125] <Business schedule execution log display process> Next, the work schedule execution log display process performed by the PC 10 will be described with reference to Fig. 27. This work schedule execution log display process is a process in which the PC 10 displays the work history related to the work performed by each part-time employee after the end of work for the day. Fig. 27 is a flowchart showing the control procedure of the work schedule execution log display process. The work schedule execution log display process is triggered by, for example, selecting a menu button corresponding to the item "Work Schedule Execution Log Display" on a menu screen (not shown) via the operation unit 14.

[0126] As shown in FIG. 27, when the business schedule execution log display process is started, the CPU 11 of the PC 10 first causes the display unit 15 to display the business schedule execution log display acceptance screen 56 as shown in FIG. 28 (step S91).

[0127] Next, the CPU 11 accepts input of the name of the part-time employee (person in charge) for which the work schedule execution log is to be displayed in the text box 561 provided on the work schedule execution log display acceptance screen 56 (step S92).

[0128] Next, the CPU 11 determines whether or not the execution button 562 provided on the business schedule execution log display acceptance screen 56 has been pressed (step S93).

[0129] In step S93, if it is determined that the execution button 562 has not been pressed (step S93; NO), the CPU 11 skips steps S94 and S95 and advances the process to step S96. On the other hand, if it is determined in step S93 that the execute button 562 has been pressed (step S93; YES), the CPU 11 reads out the business schedule execution log file 231 of the target part-time employee (person in charge) from the person-specific import folder 136 (step S94).

[0130] Next, based on the business schedule execution log file 231 read out in step S94, the CPU 11 displays the business schedule execution log 563 of the target part-time employee (person in charge) on the business schedule execution log display reception screen 56, as shown in FIG. 28 (step S95).

[0131] Next, the CPU 11 determines whether or not the end button 564 provided on the business schedule execution log display acceptance screen 56 has been pressed (step S96).

[0132] In step S96, when it is determined that the end button 564 has been pressed (step S96; YES), the CPU 11 ends the business schedule execution log display process. On the other hand, in step S96, if it is determined that the end button 564 has not been pressed (step S96; NO), the CPU 11 returns the process to step S92 and repeats the subsequent processes.

[0133] As described above, the CPU 21 of the handy terminal 20 accepts the input of a person in charge ID (login information), displays on the display unit 25 the business schedule to be performed today (within a specified period) by the user corresponding to the person in charge ID whose input has been accepted, and starts a business application program used for the business included in the business schedule. When displaying the business schedule, the CPU 21 also displays each of the businesses included in the business schedule in a selectable manner, and when an operation is performed to select a business from the business schedule, starts a business application program corresponding to the business. Therefore, according to the handheld terminal 20, it is possible to start only the business application programs corresponding to the business operations included in today's business schedule, thereby preventing the execution of business operations that do not actually need to be performed.

[0134] Furthermore, when the CPU 21 of the handy terminal 20 displays the task schedule on the display unit 25, it also displays the task execution time of the tasks included in the task schedule. Therefore, the handy terminal 20 can display the task execution time of a task included in the task schedule, thereby enabling the logged-in user (person in charge) to smoothly execute the task.

[0135] In addition, when the CPU 21 of the handheld terminal 20 obtains today's business schedule data Da1 from the PC 10, it obtains business data as work instruction information for the business to be performed by the logged-in user, and when a business application program is started, it displays on the display unit 25 work processing screens 54, 55 in a mode that allows only processing based on the business data of the corresponding business. Therefore, according to the handheld terminal 20, by displaying the work processing screens 54, 55 on the display unit 25 when performing a task, it is possible to prevent the performance of tasks that do not actually need to be performed, thereby improving the efficiency of the tasks to be performed.

[0136] In addition, the CPU 21 of the handy terminal 20 records the results (task processing information) input on the task processing screens 54, 55 in the task data, and transmits the task data to the PC 10 when the task to be performed by the logged-in user today is completed. Therefore, by transmitting the results of the work performed using the handy terminal 20 to the PC 10, the results can be managed in a centralized manner in the PC 10.

[0137] In addition, the CPU 21 of the handheld terminal 20 records a business schedule execution log (work time information) indicating the start and end times of processing based on business data, and transmits the business schedule execution log file 231 to the PC 10 when the business to be performed by the logged-in user today is completed. Therefore, by transmitting the task schedule execution log file 231 of the task performed using the handy terminal 20 to the PC 10, the status of the task performed using the handy terminal 20 can be confirmed on the PC 10.

[0138] Although the present invention has been specifically described based on the embodiment, the present invention is not limited to the above embodiment and can be modified without departing from the gist of the present invention. For example, in the above embodiment, if it is determined in step S34 of the HT task execution control process (see FIG. 17) that there is no target task schedule data Da1, the CPU 21 is configured to display the normal task menu screen on the display unit 25, but it may also be configured to display on this normal task menu screen that there is no task to be performed today.

[0139] In addition, in the above embodiment, the extraction conditions can be changed by inputting text into the text box 423 of the detailed setting screen 42 (see FIG. 15). However, for example, the extraction conditions may be changed by selecting a desired menu from a pre-provided pull-down menu.

[0140] In the above embodiment, the flash memory of the storage unit 23 is used as a computer-readable medium for the program according to the present invention, but the present invention is not limited to this example. As other computer-readable media, portable recording media such as CD-ROMs can be applied. In addition, carrier waves can be applied to the present invention as a medium for providing data of the program according to the present invention via a communication line.

[0141] Although the embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and its equivalents. The inventions described in the claims originally attached to this application are set forth below. The claim numbers in the appended claims are the same as those in the claims originally attached to this application. [Note] <Claim 1> A receiving means for receiving input of login information; a display control means for displaying, on a display unit, a work schedule to be performed within a predetermined period by a user corresponding to the login information input and accepted by the accepting means; a start control means for starting a business application program used in the business included in the business schedule; Equipped with the display control means, when displaying the business schedule, displays each of the businesses included in the business schedule in a selectable manner; the start control means starts a business application program corresponding to one business when an operation for selecting one business from the business schedule is performed; A terminal device comprising: <Claim 2> A task execution time is set for each task included in the task schedule, the display control means, when displaying the business schedule on the display unit, displays the business performance times of the business tasks included in the business schedule; 2. The terminal device according to claim 1 . <Claim 3> an acquisition means for acquiring business schedule information including the business schedule and startup information of a business application program corresponding to a business included in the business schedule when the input of the login information is accepted by the acceptance means; the start control means, when an operation for selecting one task from the task schedule is performed, starts a task application program corresponding to the one task based on the start information; 3. The terminal device according to claim 1 or 2. <Claim 4> The business schedule information includes work instruction information for the business to be performed by the user within the specified period, The terminal device according to claim 3, characterized in that, when a business application program corresponding to the one of the business tasks is launched by the launch control means, the display control means causes the display unit to display a work processing screen in a manner that enables only processing based on the work instruction information of the one of the business tasks. <Claim 5> a first recording means for recording the work processing information input on the work processing screen; A transmitting means for transmitting the work processing information recorded by the first recording means to a predetermined external device; Equipped with 5. The terminal device according to claim 4, wherein the transmission means transmits the task processing information to the external device when a task to be performed by the user within the predetermined period is completed. <Claim 6> a second recording means for recording work time information indicating a start time and an end time of a process based on the work instruction information; 6. The terminal device according to claim 5, wherein the transmission means transmits the task time information together with the task processing information to the external device when a task to be performed by the user within the predetermined period is completed. <Claim 7> The terminal device according to any one of claims 3 to 6, characterized in that, when the business schedule information is not acquired by the acquisition means, the display control means causes the display unit to display a message indicating that there is no business to be performed by the user within the specified period. <Claim 8> 8. The terminal device according to claim 1, wherein the start control means restricts the start of a business application program that is not related to the business included in the business schedule. <Claim 9> A terminal device and a management device are provided, The management device includes: a generating means for generating, for each user of the terminal device, task schedule information including a task schedule to be performed by the user within a predetermined period and startup information of a task application program corresponding to the task included in the task schedule; The terminal device A receiving means for receiving input of login information; an acquisition means for acquiring, from the management device, the work schedule information of the user corresponding to the login information input and accepted by the acceptance means; a display control means for displaying, on a display unit, the business schedule included in the business schedule information acquired by the acquisition means; a start control means for starting a business application program used in the business included in the business schedule; Equipped with the display control means, when displaying the business schedule, displays each of the businesses included in the business schedule in a selectable manner; the start control means starts a business application program corresponding to one business when an operation for selecting one business from the business schedule is performed; A business management system characterized by: <Claim 10> The terminal device computer, A receiving means for receiving input of login information; a display control means for displaying, on a display unit, a work schedule to be performed within a predetermined period by a user corresponding to the login information input and accepted by the accepting means; a start control means for starting a business application program used in the business included in the business schedule; Functioning as a the display control means, when displaying the business schedule, displays each of the businesses included in the business schedule in a selectable manner; the start control means starts a business application program corresponding to one business when an operation for selecting one business from the business schedule is performed; A program characterized by: [Explanation of symbols]

[0142] 100 Sales Management System 1 PC 11 CPU 12 RAM 13 Storage section 131 Product Master File 132 Order slip file 133 Inventory Master File 134 HT Business List File 135 Folder by Person in Charge 136 Import Folder by Person in Charge 14 Control section 15 Display 16 Communications Department 17 Timing section 2. Handheld terminal 21 CPU (acceptance means, display control means, start control means, acquisition means, first recording means, transmission means, second recording means) 22 RAM 23 Memory section 231 Business schedule execution log file 24 Control section 25 Display section 26 Communications Department 27 Scanner section 28 Timing section

Claims

1. A receiving means for receiving input of login information; a display control means for displaying, on a display unit, a work schedule to be performed within a predetermined period by a user corresponding to the login information input and accepted by the accepting means; a start control means for starting a business application program used in the business included in the business schedule; a first recording means for recording work processing information; a transmitting means for transmitting the work processing information recorded by the first recording means to a predetermined external device; Equipped with the display control means, when displaying the business schedule, displays each of the businesses included in the business schedule in a selectable manner; when an operation for selecting one task from the task schedule is performed, the start control means starts a task application program corresponding to the one task, and the display control means displays on the display unit a task processing screen for receiving input of the task processing information related to the one task; the first recording means records the work processing information input on the work processing screen; the transmission means transmits the work processing information recorded by the first recording means to the predetermined external device in response to an operation of selecting a task completion button displayed in a selectable manner on the display unit by the display control means when any of the tasks included in the task schedule is completed; A terminal device comprising:

2. The display control means, when none of the tasks included in the task schedule has been completed, does not display the task completion button on the display unit, or displays the task completion button on the display unit in an unselectable manner.

2. The terminal device according to claim 1 .

3. A second recording means for recording work time information indicating the start time and end time of a task performed by displaying the work processing screen, 3. The terminal device according to claim 1, wherein the transmission means transmits the task time information together with the task processing information to the external device in response to an operation of selecting the task completion button.

4. an acquisition means for acquiring business schedule information including the business schedule and startup information of a business application program corresponding to a business included in the business schedule when the input of the login information is accepted by the acceptance means; the start control means, when an operation for selecting one task from the task schedule is performed, starts a task application program corresponding to the one task based on the start information; 4. The terminal device according to claim 1, wherein the first and second terminals are connected to each other.

5. The business schedule information includes work instruction information for the business to be performed by the user within the specified period, The terminal device according to claim 4, characterized in that, when a business application program corresponding to the one business is launched by the launch control means, the display control means causes the display unit to display the work processing screen in a manner that enables only processing based on the work instruction information for the one business.

6. The terminal device according to claim 4 or 5, characterized in that, when the business schedule information is not acquired by the acquisition means, the display control means causes the display unit to display a message indicating that there is no business to be performed by the user within the specified period.

7. A terminal device and a management device are provided, The management device includes: a generating means for generating, for each user of the terminal device, task schedule information including a task schedule to be performed by the user within a predetermined period and startup information of a task application program corresponding to the task included in the task schedule; The terminal device A receiving means for receiving input of login information; an acquisition means for acquiring, from the management device, the work schedule information of the user corresponding to the login information input and accepted by the acceptance means; a display control means for displaying, on a display unit, the business schedule included in the business schedule information acquired by the acquisition means; a start control means for starting a business application program used in the business included in the business schedule; a first recording means for recording work processing information; a transmission means for transmitting the work processing information recorded by the first recording means to the management device; Equipped with the display control means, when displaying the business schedule, displays each of the businesses included in the business schedule in a selectable manner; when an operation for selecting one task from the task schedule is performed, the start control means starts a task application program corresponding to the one task, and the display control means displays on the display unit a task processing screen for receiving input of the task processing information related to the one task; the first recording means records the work processing information input on the work processing screen; the transmission means transmits the work processing information recorded by the first recording means to the management device in response to an operation of selecting a work completion button displayed in a selectable manner on the display unit by the display control means when any of the works included in the work schedule is completed; A business management system characterized by:

8. The terminal device computer, A receiving means for receiving input of login information; a display control means for displaying, on a display unit, a work schedule to be performed within a predetermined period by a user corresponding to the login information input and accepted by the accepting means; a start control means for starting a business application program used in the business included in the business schedule; a first recording means for recording work processing information; a transmitting means for transmitting the work processing information recorded by the first recording means to a predetermined external device; Function as a the display control means, when displaying the business schedule, displays each of the businesses included in the business schedule in a selectable manner; when an operation for selecting one task from the task schedule is performed, the start control means starts a task application program corresponding to the one task, and the display control means displays on the display unit a task processing screen for receiving input of the task processing information related to the one task; the first recording means records the work processing information input on the work processing screen; the transmission means transmits the work processing information recorded by the first recording means to the predetermined external device in response to an operation of selecting a task completion button displayed in a selectable manner on the display unit by the display control means when any of the tasks included in the task schedule is completed; A program characterized by:

Images