JP6581689B1 - Order management system, order management apparatus, and program - Google Patents

Abstract

An item input once at the time of reception registration can be used for reception registration at other facilities. An order management system for managing an order waiting group of an order waiting group at a plurality of facilities, an order management server for managing information on an order waiting registration at each facility, and a user who has registered the order waiting A user terminal possessed, and the order management server stores a waiting list for holding the waiting order status information of the user who has registered the waiting order in each facility, and the order has arrived, Selection of the next waiting list registration confirmation unit for notifying the user terminal of the user whose status is already informed of the necessity confirmation of the next waiting list registration and the user terminal selecting to perform the next waiting list registration In the case where the registration is made, a registration registration execution unit for taking over the data registered at the time of registration at the previous facility and registering the waiting at the next facility is provided. [Selection] Figure 4

Description

  The present invention relates to an order management system, an order management apparatus, and a program.

  2. Description of the Related Art Conventionally, various order management systems have been employed in restaurants, stores, hospitals, banks, government offices, and the like in order to manage waiting for customers waiting for their services.

  For example, Patent Literature 1 describes a reservation management system that simultaneously provides a reservation management service for a plurality of facilities that can wait for a turn, and a user can access the congestion of facilities from the Web, a telephone, or a store terminal. It states that you can check the situation and apply for a waiting list. In addition, it is described that notification is made by telephone or e-mail when the order of guidance approaches.

JP 2005-50002 A

  In a conventional order management system, when registering a waiting order, items necessary for reception, such as an e-mail address, must be input for each facility.

  The present invention has been made in view of the above-described circumstances, and an object of the present invention is to make it possible to use items once input at the time of registration for reception and registration at other facilities.

An order management system according to an embodiment of the present invention is an order management system that manages the waiting for an order of a waiting group in a plurality of facilities,
An order management server for managing the information of registrations waiting in turn at each facility;
A user terminal possessed by the user who registered the waiting queue,
The order management server
A storage unit for storing a waiting list for holding status information of waiting for users who have registered waiting in each facility;
The turn waiting registration necessity confirmation notifying unit for notifying the necessity confirmation of the next turn waiting registration to the user terminal of the user whose order has arrived and the status is already guided,
In the user terminal, when it is selected to register for the next waiting queue, the data registered at the time of the waiting waiting registration at the previous facility is taken over and the waiting waiting at the next facility is registered. A reception registration execution unit.

  In addition, the reception registration execution unit notifies the user terminal of a candidate for a facility that satisfies a predetermined condition when the user terminal is selected to perform the next waiting registration, and the user terminal You may make it display the reception screen of the facility selected in (1) on the user terminal.

  The predetermined condition may be within a certain distance from the previous facility.

  Further, the predetermined condition may be a facility of an industry set according to the industry of the previous facility.

  In addition, when a two-dimensional code issued at the time of waiting registration is read by the user terminal, the user terminal comprises a waiting information providing unit that provides information on the waiting state of the user to the user terminal, The turn waiting information providing unit may provide turn waiting status information about the latest turn waiting registration of the user.

  According to the present invention, items once entered at the time of reception registration can be used for reception registration at other facilities.

The figure which shows schematic structure of the order management system 1000 which concerns on embodiment of this invention. The block diagram which shows the main structures of the order management terminal 200. FIG. The sequence diagram of the reception registration process of waiting for the order in the order management system 1000 according to the embodiment of the present invention. The sequence diagram of a process when the status in the order management system 1000 which concerns on embodiment of this invention is already guided. The figure which illustrates the screen which notifies the necessity confirmation of the next waiting registration which is displayed on the user terminal 300 which concerns on embodiment of this invention. The figure which illustrates the screen which presents the candidate of the facility which registers the waiting for the next turn displayed on the user terminal 300 which concerns on embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In addition, the same code | symbol is attached | subjected to the same element and the overlapping description is abbreviate | omitted.

  In the present embodiment, an example of waiting-list management when the hospital A and the pharmacy B are continuously used will be described. In addition, restaurants, amusement facilities, shopping malls, department stores, government offices, repair shops, banks, travel agents It can be applied to any facility that manages the waiting of facility users, such as stores.

  FIG. 1 is a diagram showing a schematic configuration of an order management system 1000 according to the present embodiment. As shown in FIG. 1, the order management system 1000 includes an order management server (order management apparatus) 100 installed in a management center and the like, an order management terminal 200 installed near the entrance of a store (facility), and the like. A user terminal 300 owned by a user who visits the store is included. The order management server 100 is connected to the order management terminal 200 and the user terminal 300 via the communication network N.

  The order management server 100 manages the waiting for the order registered via the order management terminal 200 for each facility. In the example of FIG. 1, only the order management terminal 200 of one facility is illustrated, but the order management server 100 is actually connected to the order management terminal 200 installed in a plurality of facilities through a communication network. We manage the waiting order of each facility. The order management server 100 is configured by a general-purpose computer, and a server function is realized by operating a predetermined server program on the computer. The number of computers constituting the order management server 100 is not necessarily one, and may be composed of a plurality of computers distributed on the communication network N.

  The order management server 100 includes a management database (storage unit) 110 for managing the order management terminal 200 for each facility, and a processor (order waiting registration necessity confirmation notifying unit, reception registration executing unit, order waiting information providing unit) 120. And. The management database 110 includes a client management table TA1 and a status management table TA2.

  In the client management table TA1, a unique ID and a passcode (account) assigned to the order management terminal 200 are registered for each facility. For example, “ID: A1...”, “Passcode: AA2. In addition, location information (latitude / longitude) of each facility and information on the type of business (“medical institution” for hospital A, “pharmacy” for pharmacy B, etc.) are registered. These pieces of information are set by, for example, an administrator (for example, the owner of a facility) who performs management waiting in each facility at the time of system introduction. When a plurality of order management terminals 200 are used in one facility, the same ID and passcode may be used. For example, a plurality of IDs and passwords may be used properly according to predetermined conditions. .

  In the status management table TA2, a waiting list for each facility is registered. The order waiting list includes a list of persons who are waiting for an order (order waiting group) and information (status information) indicating a waiting state of each order waiting group. One record in the waiting list includes a reception number “201”, a reception time “13:03”, a status “calling”, a reception item “internal medicine”, a nickname “ABC”, and an email address “abc@xyz.co.jp”. "Is included. In addition, information such as name and telephone number can be included.

  The status includes “Waiting” which is the state before the order arrives, “Calling” which is the state informing that the order has arrived, and “Guidance” which is the state where the person who has arrived is actually guided to the seat etc. "Completed", and "cancelled", which is a state in which the waiting for the order is canceled, is included. What items are set as the status can be appropriately set and changed by the manager of each facility.

  The reception item is an item that can be selected at the time of reception registration. In the case of Hospital A, the user selects a department that waits in turn as the reception item.

  The e-mail address is an e-mail address that is temporarily registered when the user performs waiting registration from the user terminal 300. When the e-mail address is provisionally registered, the URL (Uniform Resource Locator) of the site that performs the waiting registration is transmitted to the registered address. The registered mail address can also be used as an address for receiving a call notification when the order arrives.

  Note that the information included in the waiting list can be appropriately set and changed by the manager of each facility. For example, in the case of a restaurant, information such as the number of waiting groups can be included. The contents of the records in the waiting list are updated based on new registration information in the waiting list transmitted from the order management terminal 200 or status update information (details will be described later).

  The processor 120 includes an arithmetic and logic unit (such as a CPU) that processes arithmetic operations, logic operations, bit operations, and the like and various registers, and manages the order by executing various programs stored in storage means such as a ROM. Each part of the server 100 is centrally controlled. In addition, the processor 120 also executes a computer program (order management application) for managing turn waiting in cooperation with the order management terminal 200 and the user terminal 300.

  The communication network N includes a communication network capable of transmitting and receiving information to and from each other, such as between the order management server 100, the order management terminal 200, and the user terminal 300. The communication network N is, for example, the Internet, a LAN, a dedicated line, a telephone line, a corporate network, a mobile communication network, Bluetooth (registered trademark), WiFi (Wireless Fidelity), other communication lines, or a combination thereof. It does not matter whether it is wired or wireless.

  The order management terminal 200 can exchange data with the order management server 100 via the communication network N, such as a tablet terminal, a personal computer (PC), a notebook PC, a smartphone, a mobile phone, and a personal digital assistant (PDA). A terminal device can be used. Note that a plurality of order management terminals 200 can be used in one facility.

  FIG. 2 is a block diagram showing the main configuration of the order management terminal 200. The order management terminal 200 includes a processor 210, an input device 215, a display device 216, a communication interface 220, and a storage resource 230. The order management terminal 200 accepts inputs such as registration and update to the waiting list by the facility user or employee directly operating the input device 215 such as a touch panel. For example, the employee of the facility performs an input for newly registering the waiting list in the waiting list or an input for updating the status registered in the waiting list.

  The processor 210 includes an arithmetic logic unit (CPU or the like) that processes arithmetic operations, logic operations, bit operations, and the like and various registers, and executes various programs stored in the storage resource 230 to execute the order management terminal 200. Central control of each part. The various registers are, for example, a program counter, a data register, an instruction register, a general-purpose register, and the like.

  The input device 215 includes various operation buttons and a touch panel 215a for accepting an input such as acceptance to the waiting list or disappearance from the waiting list.

  The display device 216 is a device for displaying a waiting list, a reception screen, and a status management screen, and is configured by a liquid crystal display, for example.

  The communication interface 220 is a hardware module for connecting to the communication network N and communicating with other devices via the communication network N. The communication interface 220 is a modulation / demodulation device such as an ISDN modem, an ADSL modem, a cable modem, an optical modem, or a soft modem.

  The storage resource 230 is, for example, a logical device provided by a storage area of a physical device. The physical device is a computer-readable recording medium such as a disk drive or a semiconductor memory (ROM, RAM, etc.). The storage resource 230 may be constructed by mapping a plurality of physical devices to one logical device, or may be constructed by mapping one physical device to a plurality of logical devices.

  The storage resource 230 stores an operating system program, a driver program, various data, and the like. Examples of the driver program include a communication interface driver program for controlling the communication interface 220. In addition to these various programs and various data, the storage resource 230 includes a computer program (order management application for managing turn waiting in cooperation with the order management server 100 and the user terminal 300 by being executed by the processor 210. ) AP1 is stored.

  The user terminal 300 is a terminal, such as a smartphone, a mobile phone, a tablet terminal, a personal computer (PC), a notebook PC, or a wearable device, owned by a facility user. The user terminal 300 includes a processor 310, an input device 320 such as various operation buttons and a touch panel, a display device 330 such as a liquid crystal display, a communication interface 340 for connecting to the communication network N, a disk drive or a semiconductor memory (ROM, RAM, etc.). The storage resource 350 is provided. In addition to these various programs and various data, the storage resource 350 stores a computer program (dedicated application) for managing turn waiting in cooperation with the order management server 100. The user can register the waiting order for each facility or check the waiting state via a dedicated application or web browser installed in the user terminal 300.

(Registration waiting for waiting)
Next, the waiting-order reception registration process by the order management system 1000 will be described with reference to the sequence diagram of FIG. The user who performs reception registration may actually go to the facility and operate the order management terminal 200, or can perform reception registration through the user terminal 300 owned by the user. When the user terminal 300 is used, the user can perform registration for registration from home or away from home. Specifically, it is possible to register for reception by displaying a reception screen of a facility to be used on a dedicated application or website. Here, a case where the user terminal 300 is used will be described as an example.

  First, the user operates the user terminal 300 to access the website of the order management system 1000, and performs an operation of selecting a facility (here, hospital A) to be used (step S101).

  When a facility to be used is selected, the user terminal 300 displays a mail address input screen on the display device 330 and accepts an input of a mail address (step S102).

  When the input of the e-mail address is completed, the user terminal 300 transmits the facility identification information (facility name or facility ID, etc.) selected to the order management server 100 and the input e-mail address (step S103).

  The order management server 100 transmits a URL for displaying the reception screen of the received facility to the received mail address (step S104).

  The user operates the user terminal 300 to access the received URL and display the hospital A reception screen (step S105). Information such as the current waiting time of hospital A is displayed on the reception screen. The user operates the user terminal 300 to complete the input of information (nickname, reception item, presence / absence of call notification (telephone or e-mail), contact information at the time of call), etc. necessary for reception of waiting in order .

  When the input of information necessary for the waiting for reception is completed, the input information (new registration information) is transmitted from the user terminal 300 to the order management server 100 (step S106).

  Based on the received new registration information, the order management server 100 performs a process of newly adding a set of waiting orders to the waiting list of the facility (hospital A) (step S107).

  On the user terminal 300, a reception completion screen is displayed, and a reception number, an expected waiting time at the present time, and the like are displayed (step S108).

  In addition, when the user performs reception registration from the order management terminal 200, a message prompting to receive the turn ticket is displayed on the reception completion screen together with the reception number and the expected waiting time. A pass ticket printed from a printer connected to the printer can be received. The two-dimensional code associated with the receipt number is printed on the turn ticket, and when the user reads the two-dimensional code using the user terminal 300, the user terminal 300 receives the current order of the user. The waiting status (current number of waiting groups, expected waiting time, etc.) is displayed.

(Update waiting list)
The contents of each record in the waiting list of each facility are updated when the facility employee performs operations such as “cancel”, “change”, “call”, “guidance” using the order management terminal 200. The “Cancel” means canceling the waiting order, and “change” means changing the contents of the waiting order once input. In addition, “call” means that the group that has been ordered is called verbally or informed by telephone or call mail. “Guidance” actually corresponds to the group that has been ordered. It means that it is in the state which started.

  The employee selects the waiting group to be updated from the waiting list displayed on the order management terminal 200, and “cancel”, “change”, “call”, “ Update one of the “Guidance”. Information (for example, reception number “1”) for specifying the order waiting group to be updated and update operation information (for example, “call”) are uploaded from the order management terminal 200 to the order management server 100 via the communication network N. . The order management server 100 updates the waiting list for the facility based on the received information. For example, when the “calling” operation is performed on the reception number “1”, the status of the waiting group in the reception number “1” is updated to “calling”.

(Processing at the time of guidance)
Next, processing when the user is guided and the status is already guided at the facility where the waiting is registered will be described with reference to the sequence diagram of FIG.

  When the status of the waiting group registered in the waiting list becomes “Guided” (step S201: YES), the order management server 100 requires the next waiting list registration to the user terminal 300 of the waiting group. A rejection confirmation is notified (step S202). The notification may be email notification, push notification, or the like. Moreover, you may display on the screen displayed when the user terminal 300 reads a two-dimensional code.

  FIG. 5 is a diagram exemplifying a screen that is displayed on the user terminal 300 and notifies the necessity confirmation of the next waiting registration. As shown in FIG. 5, it is shown that the next waiting order can be registered by using the current registration information (data registered at the time of hospital A registration). Also, information (e-mail address, nickname, number of people, etc.) that can be used for the next registration is displayed.

  When the user performs an operation for selecting registration of the next waiting queue (operation of the button B) (step S203: YES), the order management server 100 may select a facility candidate for registering the waiting queue in the user terminal 300. Is displayed (step S204).

  FIG. 6 is a diagram exemplifying a screen that presents candidate facilities to be registered for waiting for the next turn. As shown in FIG. 6, a plurality of facilities (pharmacies and restaurants) are displayed as candidates. The order management server 100 is a facility of a predetermined industry among the facilities registered in the client management table TA1, and the distance from the most recently registered facility (here, hospital A) is within a certain value ( For example, facilities within 1 km) are displayed.

  As the business type, for example, a business type that is frequently registered next to the most recently registered facility may be set in advance based on statistical information such as the actual usage status, and may be stored in the order management server 100. For example, if the type of industry that has a certain frequency or more after the hospital (medical institution) is “pharmacy” or “restaurant”, the candidate for registration after “medical institution” Display "pharmacy" and "restaurant" within distance.

  When the user performs an operation of selecting one of the facilities displayed on the user terminal 300, the order management server 100 displays a reception screen for the selected facility on the user terminal 300 (step S205). Here, since the e-mail address has already been registered at the time of the waiting registration for the hospital A, the temporary registration of the e-mail address and the notification of the URL are omitted. In addition, a part of the previously registered data (such as a nickname) is inherited as it is.

  When the user completes inputting other necessary information, the input information (new registration information) is transmitted from the user terminal 300 to the order management server 100 (step S206).

  Based on the received new registration information, the order management server 100 performs a process of newly adding one set of waiting orders to the waiting list of the facility (pharmacy B) (step S207). The reception number is assigned a number (here, “201-1”) associated with the previous reception number (here, “201”). For example, information such as reception number “201-1”, reception time “14:00”, status “waiting”, nickname “ABC”, mail address “abc@xyz.co.jp” is registered in the record. The

  On the user terminal 300, a reception completion screen is displayed, and a reception number, a current waiting time and the like are displayed (step S208).

  Further, when the waiting status of the pharmacy B becomes “Guided”, the confirmation of the necessity for the next waiting queue registration is notified again (step S202), and when the next waiting queue registration is registered, the reception data is taken over. It is. For example, when registering the waiting order of the restaurant C, the temporary registration of the mail address and the notification of the URL are omitted, and the reception screen of the restaurant C is displayed on the user terminal 300. The reception number is assigned a number (for example, “201-2”) associated with the first reception number (here, “201”).

  In addition, the two-dimensional code of the turn ticket issued at the time of registration is also transferred to the next waiting queue registration, and the user uses the same two-dimensional code when inquiring about the waiting status of the next registered facility. be able to. Specifically, when the user reads the two-dimensional code using the user terminal 300, the latest record (status is “Guided”) among the records of the receipt numbers associated with the user. And the corresponding waiting state is displayed on the user terminal 300.

  For example, if the user terminal 300 reads the two-dimensional code issued at the time of waiting registration at the hospital A while the user is waiting at the hospital A, the waiting status at the hospital A is displayed. The On the other hand, when the status at the hospital A becomes “Guided” and the next two-dimensional code is read after registering the waiting order of the pharmacy B, the waiting situation at the pharmacy B is displayed. Further, when the status at the pharmacy B becomes “Guided”, and the next two-dimensional code is read after registering the waiting order of the restaurant C, the waiting state at the restaurant C is displayed.

  As described above, according to this embodiment, when the status is already guided, the user terminal 300 of the user is notified of the necessity confirmation of the next turn waiting registration, and the next turn waiting registration is performed. In this case, since the data used in the previous waiting registration is taken over, it is not necessary to input the reception item once input many times, and the convenience for the user is improved. In particular, when displaying the reception screen on the user terminal 300, the two steps of temporary registration of an email address and access to the notified URL can be omitted, so that the user can easily display the reception screen of the facility to be registered. Can be made.

  In addition, when the status at the facility waiting for the turn is already informed, the confirmation of the necessity for the next turn waiting registration is notified, so it is easy for the user to schedule and the previous facility Therefore, it is possible to prevent the inconvenience that the order at the next facility comes while waiting for the turn.

  In addition, when performing the next waiting registration, the user terminal 300 is displayed with the facility candidates that satisfy the predetermined condition, so that the convenience for the user to select the facility is improved. As a condition, it is possible to present a facility that is easy for the user to use by selecting a facility that is within a certain distance from the nearest facility as a candidate. In addition, as a condition, it is possible to improve the convenience of the user and increase the utilization rate of other facilities by selecting a facility of a type of industry that is highly likely to be used after using the most recent facility. .

  In addition, using the issued 2D code, it is now possible to inquire about the waiting status of the facility that registered the next waiting queue, so there is no need to issue a 2D code each time registration is registered, and the process can be simplified. At the same time, the user can save the trouble of managing a plurality of two-dimensional codes.

  The present invention is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the gist of the present invention. For this reason, the said embodiment is only a mere illustration in all points, and is not interpreted limitedly. For example, the above-described processing steps can be arbitrarily changed in order as long as the processing contents do not contradict each other, or can be executed in parallel.

1000 ... Order management system 100 ... Order management server 110 ... Management database 120 ... Processor 200 ... Order management terminal 210 ... Processor 215 ... Input device 215a ... Touch panel 216 ... Display device 220 ... Communication interface 230 ... Storage resource 300 ... User terminal 310 ... Processor 320 ... Input device 330 ... Display device 340 ... Communication interface 350 ... Storage resource TA1 ... Client management table TA2 ... Status management table N ... Communication network AP1 ... Order management application

Claims (7)

An order management system for managing the waiting order of a waiting group in a plurality of facilities,
An order management server for managing the information of registrations waiting in turn at each facility;
A user terminal possessed by the user who registered the waiting queue,
The order management server
A storage unit for storing a waiting list for holding status information of waiting for users who have registered waiting in each facility;
The turn waiting registration necessity confirmation notifying unit for notifying the necessity confirmation of the next turn waiting registration to the user terminal of the user whose order has arrived and the status is already guided,
In the user terminal, when it is selected to register for the next waiting queue, the data registered at the time of the waiting waiting registration at the previous facility is taken over and the waiting waiting at the next facility is registered. An order management system comprising: a reception registration execution unit. The reception registration execution unit
In the user terminal, when it is selected to perform the next waiting registration, the user terminal is notified of facility candidates that satisfy a predetermined condition,
The order management system according to claim 1, wherein a reception screen for a facility selected on the user terminal is displayed on the user terminal. The predetermined condition is:
The order management system according to claim 2, wherein the order management system is within a certain distance from the previous facility. The predetermined condition is:
The order management system according to claim 2, wherein the order management system is a facility of a business type set according to a business type of the previous facility. When a two-dimensional code issued at the time of waiting registration is read by the user terminal, the user terminal includes a waiting information providing unit that provides information on the waiting state of the user to the user terminal,
The waiting information providing unit
The order management system according to any one of claims 1 to 4, which provides information on an order waiting status regarding registration of the latest waiting order of the user. It is an order management device that manages the waiting order of a waiting group in a plurality of facilities,
A storage unit for storing a waiting list for holding status information of waiting for users who have registered waiting in each facility;
A turn waiting registration necessity confirmation notifying part for notifying the necessity confirmation of the next turn waiting registration to the user terminal of the user whose order has arrived and the status has been guided,
In the user terminal, when it is selected to register for the next waiting queue, the data registered at the time of the waiting waiting registration at the previous facility is taken over and the waiting waiting at the next facility is registered. An order management device comprising: a reception registration execution unit. A computer that manages the waiting list of waiting groups in multiple facilities,
A storage unit for storing a waiting list for holding status information of waiting for users who have registered waiting in each facility;
A turn waiting registration necessity confirmation notifying part for notifying the necessity confirmation of the next turn waiting registration to the user terminal of the user whose order has arrived and the status has been guided,
In the user terminal, when it is selected to register for the next waiting queue, the data registered at the time of the waiting waiting registration at the previous facility is taken over and the waiting waiting at the next facility is registered. A program that functions as a reception registration execution unit.