Program, method, server device, and beauty management system

Abstract

This program to be executed by a server device (20), which is provided with a processor (21) and a memory (22) and which manages a beauty appliance that performs beauty treatment on customers, causes the processor (21) to execute: a step for acquiring usage records of the beauty device (10); a step for aggregating the acquired usage records; and a step for outputting, to a user terminal used by a user, in response to an access request from the user terminal, a dashboard screen showing the results of the aggregation of the usage records for each store that provides the beauty treatment.

Description

Program, method, server device, and beauty management system

[0001] The present disclosure relates to a program, a method, a server device, and a beauty management system.

[0002] Conventionally, beauty devices that utilize high-frequency dielectric heating have been known. Patent Document 1 discloses a beauty device that applies heat to deep parts of the skin to promote blood circulation.

[0003] Japanese Patent Application Publication No. 1-277578

[0004] Such beauty devices are sometimes used by store staff in beauty salons and other beauty businesses that provide beauty treatments to customers. In such cases, the usage record of the beauty devices is not quantitatively managed, which has led to the problem of not being able to provide appropriate beauty treatments using the beauty devices to customers.

[0005] The present disclosure aims to provide a program, method, server device, and beauty management system that can provide suggestions regarding appropriate beauty treatments to stores operating in the beauty business.

[0006] One aspect of the present disclosure is a program to be executed by a server device that has a processor and memory and manages beauty equipment that performs beauty treatments on customers, the program causing the processor to perform the following steps: acquiring usage history of the beauty equipment; aggregating the acquired usage history; and, in response to an access request from a user terminal used by a user, outputting to the user terminal a dashboard screen showing the aggregated results of the usage history for each store that provides the beauty treatment.

[0007] A method executed by a server device equipped with a processor and memory and managing beauty equipment for providing beauty treatments to customers includes the steps of the processor acquiring usage records of the beauty equipment, aggregating the acquired usage records, and, in response to an access request from a user terminal used by a user, outputting to the user terminal a dashboard screen showing the aggregated results of the usage records for each store that provides the beauty treatments.

[0008] A server device equipped with a processor and memory and managing beauty equipment for providing beauty treatments to customers has the processor equipped with a module for acquiring usage records of the beauty equipment, a module for aggregating the acquired usage records, and a module for outputting to the user terminal, in response to an access request from a user terminal used by the user, a dashboard screen showing the aggregated results of the usage records for each store that provides the beauty treatments.

[0009] In the beauty management system comprising the server device and the beauty device, the beauty device comprises a first oscillator circuit that generates a high-frequency voltage, an electromagnetic wave probe having an electrode to which the high-frequency voltage is applied to perform dielectric heating, a second oscillator circuit that generates an AC signal of a predetermined frequency, an ultrasonic probe having a vibrator that vibrates when the AC signal is applied, and a wireless communication module that communicates wirelessly with the server device.

[0010] According to the present disclosure, it is possible to provide suggestions regarding appropriate beauty treatments to stores operating beauty businesses.

[0011] 1 is a diagram illustrating an overview of a beauty management system of the present invention. FIG. 1 is a diagram illustrating the hardware configuration of a server shown in FIG. 1. FIG. 2 is a diagram illustrating the hardware configuration of a store terminal shown in FIG. 1. FIG. 3 is a diagram illustrating the functional configuration of the server shown in FIG. 1. FIG. 4 is a diagram illustrating an example of the configuration of a user account database. FIG. 5 is a diagram illustrating an example of the configuration of a business operator database. FIG. 6 is a diagram illustrating an example of the configuration of a store database. FIG. 7 is a diagram illustrating an example of the configuration of a device database. FIG. 8 is a diagram illustrating an example of the configuration of a treatment menu database. FIG. 9 is a diagram illustrating an example of the configuration of a usage history database. FIG. 10 is a diagram illustrating an example of the configuration of an device operation summary database. FIG. 11 is a diagram illustrating an overview of an embodiment of the present invention. FIG. 12 is a diagram illustrating an example of a first screen of the present invention. FIG. 13 is a diagram illustrating an example of a second screen of the present invention. FIG. 14 is a flow diagram illustrating the aggregation process of beauty device usage history by a beauty management system. FIG. 15 is a flow diagram illustrating the output process of a dashboard screen by a beauty management system. FIG. 16 is a flow diagram illustrating the output process of a recommended menu by a beauty management system. FIG. 17 is a flow diagram illustrating the output process of an improvement menu by a beauty management system. FIG. 18 is a flow diagram illustrating the process of remotely operating beauty devices by an administrator terminal.

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. The names and functions of the components are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0013] 1. Configuration of Beauty Management System 1 The following describes the configuration of a beauty management system 1 (hereinafter simply referred to as system 1) according to one embodiment of the present invention.

[0014] (1-1) Overall Configuration First, the overall configuration of the system 1 will be described with reference to FIG. 1. As shown in FIG. 1, the system 1 is a system used to manage beauty devices 10 that perform beauty treatments on customers. The beauty devices 10 are used by store staff in a store (e.g., a beauty salon) operated by a business operator engaged in the beauty business. The beauty devices 10 are devices that perform various beauty treatments on customers of the beauty salon. A beauty salon owns at least one beauty device 10.

[0015] System 1 can be used, for example, in an equipment rental business that rents beauty devices 10 to beauty salons. In this case, the equipment rental business may act as the administrator of system 1. Using information obtained through processing by system 1, the equipment rental business can provide consulting services regarding beauty services using the beauty devices 10 to beauty salons under rental contracts. Alternatively, the administrator of system 1 may be a system vendor commissioned by the rental business of the beauty devices 10.

[0016] Here, the beauty device 10 includes machines that perform various treatments. Examples of the beauty device 10 include: - A high-frequency beauty device (RF beauty device) that uses high-frequency (RF waves) to perform dielectric heating on the treatment area - An EMS beauty device that applies low-frequency electrical stimulation to muscles - An ultrasonic beauty device that applies ultrasonic vibrations to the treatment area In this embodiment, the beauty management system will be described using a high-frequency beauty device as an example of the beauty device 10. However, the beauty device 10 may also be a device that performs other treatments.

[0017] FIG. 1 is a diagram showing the overall configuration of system 1. As shown in FIG. 1, system 1 includes a beauty device 10, a server 20, a store terminal 30, and an administrator terminal 40. Here, users of system 1 will be described. The users of system 1 include the following: Store staff: those who use the beauty device 10 and the store terminal 30 to provide beauty treatments to customers Store manager: those who use the store terminal 30 to manage the operation of the beauty salon Administrator: those who use the administrator terminal to maintain and manage system 1 Note that the store manager may also perform beauty treatments using the beauty device 10.

[0018] The server 20 includes various computers such as a personal computer, a server computer (for example, a web server, an application server, a database server, or a combination thereof), etc. In this embodiment, the server 20 will be described as an example of a cloud server that makes one or more virtualized servers available via a network. The functional configuration of the server 20 will be described later.

[0019] The store terminal 30 is an information processing device operated by store staff of the beauty salon. The store terminal 30 is realized by a portable tablet terminal, a smartphone, a desktop personal computer (PC), a laptop PC, or the like that is compatible with the system 1. In this embodiment, a tablet terminal will be described as an example of the store terminal 30. The store terminal 30 is connected to the network 80 via wireless communication with a wireless LAN router 82. The store terminal 30 is an example of a user terminal of the present invention.

[0020] The administrator terminal 40 is an information processing device operated by an administrator who maintains and operates the system 1. The administrator terminal 40 is realized by a desktop personal computer (PC), a laptop PC, a tablet terminal, a smartphone, or the like that is compatible with the system 1. In this embodiment, a desktop PC will be described as an example of the administrator terminal 40. The administrator terminal 40 is connected to the network 80. The administrator terminal 40 is an example of a user terminal of the present invention.

[0021] (1-2) Configuration of the Cosmetic Device 10 Next, we will explain the configuration of the cosmetic device 10. As shown in Fig. 1, the cosmetic device 10 includes a control unit 11, a storage unit 12, an oscillation circuit 13, a communication IF 14, an operation panel 15, and an output probe 16.

[0022] The control unit 11 is hardware for executing an instruction set written in a program stored in the storage unit 12, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0023] The storage unit 12 is a storage device for temporarily storing programs and data processed by the programs, etc., and includes, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage unit 12 is also a storage device for saving programs and data, and includes, for example, a flash memory and an HDD (Hard Disc Drive).

[0024] The programs stored in the storage unit 12 include, for example, the following programs: a program for an application that performs a cosmetic treatment; and a program for an application that communicates with an external device.

[0025] The data stored in the memory unit 12 includes, for example, the following data: A database relating to the processing content of the cosmetic treatment A database relating to the processing results of the cosmetic treatment (the execution results of the cosmetic treatment) Data obtained by executing information processing (the execution results of the information processing) The execution results of the cosmetic treatment include an operation log of the cosmetic device 10.

[0026] The oscillator circuit 13 is an LC circuit having a coil and a capacitor, and generates a high frequency wave by vibrating while transferring energy between the coil and the capacitor.

[0027] The communication IF 14 is an interface for inputting and outputting signals so that the beauty device 10 can communicate with external devices. The communication IF 14 includes a wireless communication module. The wireless communication module wirelessly communicates with communication devices such as a wireless base station 81 that complies with communication standards such as 5G and LTE (Long Term Evolution) and a wireless LAN router 82 that complies with wireless LAN (Local Area Network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11.

[0028] The operation panel 15 is an input device for receiving input operations from the store staff. The operation panel 15 is configured with, for example, input buttons and a display. The beauty device 10 may have other input devices, such as a touchpad, a pointing device such as a mouse, and a keyboard, instead of or in addition to the operation panel 15.

[0029] The output probe 16 is an output device that emits high-frequency electromagnetic waves to customers of the beauty salon. The output probe 16 has an electrode and a handle. The electrode is electrically connected to the oscillation circuit 13. The electrode emits electromagnetic waves when a high-frequency voltage generated by the oscillation circuit 13 is applied to it.

[0030] The handle is a member that covers the electrodes with an insulating layer, and is held by a store staff member when using the beauty device 10. In this embodiment, the beauty device 10 includes two output probes 16. However, the number of output probes 16 may be one.

[0031] The server 20 is a server device that performs various calculation processes described below and provides the store terminal 30 with aggregated results regarding the usage history of the beauty device 10 via the network 80. The server 20 also provides the store terminal 30 with analysis results based on the usage history of the beauty device 10.

[0032] (1-3) Hardware Configuration of Server 20 Next, with reference to Fig. 2A, a description will be given of the hardware configuration of the server 20. As shown in Fig. 2A, the server 20 includes a processor 21, a memory 22, a storage 23, a communication IF 24, and an input / output IF 25.

[0033] The processor 21 is hardware for executing an instruction set written in a program stored in the storage 23, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0034] The memory 22 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0035] The storage 23 is a storage device for saving programs and data, and is, for example, a flash memory or a hard disk drive (HDD). The programs stored in the storage 23 include, for example, the following programs: - OS (Operating System) programs - Application programs (for example, web browsers) that execute information processing

[0036] The data stored in the storage 23 includes, for example, the following data: Databases referenced in information processing Data obtained by executing information processing (i.e., execution results of information processing)

[0037] The communication IF 24 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0038] The input / output IF 25 functions as an input device for accepting input operations via the store terminal 30 and the manager terminal 40, and as an interface with an output device for presenting information to the store terminal 30 and the manager terminal 40.

[0039] (1-4) Hardware Configuration of Store Terminal 30 Next, the hardware configuration of the store terminal 30 will be described with reference to Fig. 2B. Fig. 2B is a diagram showing the hardware configuration of the store terminal 30. As shown in Fig. 2B, the store terminal 30 includes a processor 31, memory 32, storage 33, a communication IF (Interface) 34, an input device 35, and an output device 36. The hardware configuration of the manager terminal 40 is generally the same as that of the store terminal 30, and therefore a description thereof will be omitted.

[0040] The store terminal 30 is communicably connected to the server 20 via a network 80. The store terminal 30 is connected to the network 80 by wirelessly communicating with communication devices such as a wireless base station 81 that complies with communication standards such as 5G and LTE (Long Term Evolution), and a wireless LAN router 82 that complies with wireless LAN (Local Area Network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11.

[0041] The processor 31 is hardware for executing an instruction set written in a program stored in the storage 33, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0042] The memory 32 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0043] The storage 33 is a storage device for saving programs and data, and is, for example, a flash memory or a hard disk drive (HDD). The programs stored in the storage 33 include, for example, the following programs: - OS (Operating System) programs - Application programs (for example, web browsers) that execute information processing

[0044] The data stored in the storage 33 includes, for example, the following data: Databases referenced in information processing Data obtained by executing information processing (execution results of information processing)

[0045] The communication IF 34 is an interface for inputting and outputting signals so that the store terminal 30 can communicate with external devices.

[0046] The input device 35 is an input device (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.) for receiving input operations from a user.

[0047] The output device 36 is an output device (such as a display or speaker) for presenting information to the user. The output device 36 displays data such as images, videos, and text in response to processing by the processor 31. The output device 36 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0048] The processor 31 presents information to the user by displaying the information on the output device 36. The processor 31 has a function as a web browser. That is, the processor 31 accesses the data transmission path (TCP connection) between the server 20 and the store terminal 30, and performs rendering processing to display the dashboard screen of the system 1, which the server 20 has output to the data transmission path, on the output device 36. The dashboard screen of the system 1 will be described later.

[0049] (1-5) Functional Configuration of Server 20 Next, the functional configuration of the server 20 will be described with reference to Fig. 3. Fig. 3 is a diagram showing the functional configuration of the server 20. As shown in Fig. 3, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0050] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0051] The storage unit 202 stores data and programs used by the server 20. The storage unit 202 stores, for example, the following databases: User account database (user account DB) 2021, business operator database (business DB) 2022, store database (store DB) 2023, equipment database (equipment DB) 2024, treatment menu database (treatment menu DB) 2025, usage record database (usage record DB) 2026, equipment operation summary database (equipment operation summary DB) 2027, and treatment summary database (treatment summary DB) 2028.

[0052] The user account DB 2021 is a database that manages user account information. The data structure of the user account DB 2021 will be described in detail later.

[0053] The business operator DB 2022 is a database that manages information about business operators that use the system 1. The data structure of the business operator DB 2022 will be described in detail later.

[0054] The store DB 2023 is a database that manages information about beauty salons that use the system 1. The data structure of the store DB 2023 will be described in detail later.

[0055] The device DB 2024 is a database that manages information about the beauty devices 10 managed by the system 1. The data structure of the device DB 2024 will be described in detail later.

[0056] The treatment menu DB 2025 is a database that manages the contents (treatment menus) of beauty treatments to be performed on customers using the beauty device 10. The data structure of the treatment menu DB 2025 will be described in detail below.

[0057] The usage history DB 2026 is a database that manages the usage history of the beauty device 10. The data structure of the usage history DB 2026 will be described in detail later.

[0058] The device operation summary DB 2027 is a database that manages a summary of the operation status of the beauty device 10, which is one of the results of tallying up the usage record of the beauty device 10. The data structure of the device operation summary DB 2027 will be described in detail below.

[0059] The treatment summary DB 2028 is a database that manages summaries of treatment menus performed using the beauty device 10, among the results of tallying up the usage record of the beauty device 10. The data structure of the treatment summary DB 2028 will be described in detail below.

[0060] The control unit 203 functions as various modules when the processor 21 of the server 20 performs processing according to a program. The control unit 203 functions as a transmission / reception control module 2031, an acquisition module 2032, a counting module 2033, a specification module 2034, and an output module 2035.

[0061] The transmission / reception control module 2031 controls the processing in which the server 20 transmits and receives signals to and from external devices in accordance with a communication protocol.

[0062] The acquisition module 2032 acquires various pieces of information transmitted from the store terminal 30 or the manager terminal 40 in response to operations of the store terminal 30 or the manager terminal 40. The acquisition module 2032 records the acquired various pieces of information in the corresponding databases.

[0063] Furthermore, the acquisition module 2032 acquires information relating to usage history transmitted from the beauty device 10 in response to an operation of the beauty device 10. The acquisition module 2032 records the acquired usage history of the beauty device 10 in the usage history DB 2026. The information relating to usage history transmitted from the beauty device 10 includes, for example, the following information: Identification information of the beauty device 10 used Identification information of the treatment menu Identification information of the store staff member who used it Information about the person receiving the treatment Operating time of the beauty device 10 Date and time of data reception

[0064] The tallying module 2033 tally the acquired usage history of the beauty device 10. In response to acquisition of new usage history, the tallying module 2033 updates the tallying result of the usage history for the default value of the preset evaluation period.

[0065] The tallying module 2033 also tally the usage records of the beauty devices 10 during the specified evaluation period in response to a tallying instruction from the store terminal 30 or the manager terminal 40. The tallying module 2033 stores the tallying results of the usage records as new records in the device operation summary DB 2027 and the treatment summary DB 2028.

[0066] The identification module 2034 identifies, as a recommended menu, a treatment menu that will contribute to the management of the salon from among treatment menus that have already been performed, by referring to the usage history of the beauty device 10. Details of the process of identifying a recommended menu will be described later.

[0067] Furthermore, the identification module 2034 refers to the usage history of the beauty device 10 and identifies, as an improvement menu, a treatment menu that has a large variation in the operating time between treatments among treatment menus that have already been performed. Details of the process of identifying an improvement menu will be described later.

[0068] The output module 2035 outputs various information obtained by the executed processing in response to an operation from the store terminal 30 or the manager terminal 40. For example, in response to a login operation (access request) to the system 1 from the store terminal 30, the output module 2035 outputs information on the dashboard screen of the system 1 to the data transfer path between the store terminal 30. The dashboard screen of the system 1 will be described later.

[0069] (1-6) Data Structure Next, the data structure of each database stored in the storage unit 202 of the server 20 will be described in detail with reference to FIGS. 4A to 6B.

[0070] (1-6-1) User Account DB 2021 Fig. 4A is a diagram showing an example of the data structure of the user account DB 2021. A new record is recorded in the user account DB 2021 when a beauty salon operator that provides beauty services to customers performs a user registration operation when starting to use the system 1.

[0071] As shown in FIG. 4A, the user account DB 2021 includes the items "user ID," "account," "password," "user name," "user authority," and "affiliated store ID."

[0072] The item "user ID" stores user identification information that can identify a user who uses the system 1.

[0073] The item "account" stores account information of a user corresponding to a user ID.

[0074] The item "password" stores the login password used when the user corresponding to the user ID logs in to the system 1.

[0075] The item "user name" stores the name of the user corresponding to the user ID.

[0076] The item "user authority" stores the authority of the user corresponding to the user ID. The user authority includes, for example, the following items: Administrator authority: authority as an administrator of the system 1 Store staff authority: authority as a store staff member of the beauty salon Store manager authority: authority as a manager of the beauty salon

[0077] In the system 1, a user with administrator privileges can view the usage history of the beauty device 10 for all businesses that use the system 1. In addition, a user with administrator privileges can remotely control the beauty device 10, which will be described later.

[0078] Meanwhile, in the system 1, a user with store staff authority can view the usage history of the beauty device 10 for the store to which the user belongs. Also, in the system 1, a user with store manager authority can view the usage history of the beauty device 10 for multiple stores operated by the business operator to which the user belongs. Note that the setting of user authority is not limited to the above example and can be changed as desired.

[0079] The "Store ID" field stores the identification information of the store to which the user corresponding to the user ID belongs. If the user is a manager, the "Store ID" field is left blank. If the user has store manager authority, the field stores the IDs of multiple stores belonging to the same business.

[0080] 4A is merely an example. The user account DB 2021 may include columns in which other data items are stored.

[0081] (1-6-2) Business Operator DB 2022 Fig. 4B is a diagram showing an example of the data structure of the business operator DB 2022. A new record is recorded in the business operator DB 2022 when an operator of a beauty salon that provides beauty treatments performs a user registration operation when starting to use the system 1.

[0082] As shown in FIG. 4B, the business operator DB 2022 includes an item "business operator ID" and an item "business operator name."

[0083] The item "business ID" stores business identification information that can identify the business that operates the beauty salon.

[0084] The item "business name" stores the name of the business corresponding to the business ID.

[0085] 4B is merely an example. The business entity DB 2022 may include columns in which other data items are stored.

[0086] (1-6-3) Shop DB 2023 Fig. 4C is a diagram showing an example of the data structure of the shop DB 2023. New records are recorded in the shop DB 2023 when an operator of a beauty salon that provides beauty treatments performs a user registration operation when starting to use the system 1.

[0087] As shown in FIG. 4C, the store DB 2023 includes the items "Store ID", "Business ID", "Store Name", "Prefecture", "Location", and "Contact Information".

[0088] The item "store ID" stores store identification information that can identify the beauty salon.

[0089] The item "business ID" stores identification information of the business to which the beauty salon corresponding to the store ID belongs.

[0090] The item "store name" stores the name of the beauty salon corresponding to the store ID.

[0091] The item "Prefecture" stores the prefecture where the beauty salon corresponding to the store ID is located.

[0092] The item "location" stores information about the location of the beauty salon corresponding to the store ID.

[0093] The "contact information" field stores contact information for the beauty salon corresponding to the salon ID. The contact information includes the telephone number or email address of the salon.

[0094] 4C is merely an example. The store DB 2023 may include columns in which other data items are stored.

[0095] (1-6-4) Device DB 2024 Fig. 5A is a diagram showing an example of the data structure of the device DB 2024. A new record is recorded in the device DB 2024 when a device registration operation is performed when the beauty device 10 is first used in a store.

[0096] As shown in FIG. 5A, the device DB 2024 includes the items "Device ID", "Store ID", "Device Type ID", "Serial No", "FW Version", and "Shipping Date".

[0097] The item "device ID" stores identification information of the beauty device 10 that can identify the beauty device 10 used in the beauty salon.

[0098] The item "shop ID" stores identification information of the beauty salon where the beauty device 10 corresponding to the device ID is installed.

[0099] The item "Device Type ID" stores a device type ID that indicates the device type of the beauty device 10 corresponding to the device ID. Each beauty device 10 is assigned a unique device type ID depending on the type of device.

[0100] The item "Serial No." stores the product number of the beauty device 10 corresponding to the device ID. The product number is a unique value for each beauty device 10.

[0101] The item "FW version" stores version information of the firmware (FW) installed in the beauty device 10 corresponding to the device ID. Firmware is software stored in the storage unit 12 of the beauty device 10 that controls the processing of the beauty device 10.

[0102] The item "shipping date" stores the date on which the beauty device 10 corresponding to the device ID was shipped to the beauty salon.

[0103] 5A is merely an example, and the device DB 2024 may include columns in which other data items are stored.

[0104] (1-6-5) Treatment Menu DB 2025 Fig. 5B is a diagram showing an example of the data structure of the treatment menu DB 2025. A new record is recorded in the treatment menu DB 2025 when an operation pattern corresponding to a treatment menu is set in the beauty device 10.

[0105] As shown in FIG. 5B, the treatment menu DB 2025 includes an item "menu ID", an item "menu name", an item "device type ID", an item "treatment content", and an item "treatment fee".

[0106] The item "menu ID" stores identification information of a treatment menu that can identify the treatment menu.

[0107] The item "menu name" stores the name of the treatment menu corresponding to the menu ID.

[0108] The item "device type ID" stores the device type ID of the beauty device 10 that performs the treatment menu corresponding to the menu ID.

[0109] The item "treatment content" stores the treatment content of the treatment menu corresponding to the menu ID. The treatment content includes, for example, the operation pattern of the beauty device 10 and the treatment area. The operation pattern of the beauty device 10 includes the frequency, output intensity, output time, etc. of the electromagnetic waves to be output. The treatment content may also include the purpose of the treatment, such as slimming or promoting blood circulation.

[0110] The item "treatment fee" stores the fee received from the customer as the cost of the treatment menu corresponding to the menu ID.

[0111] 5B is merely an example. The treatment menu DB 2025 may include columns in which other data items are stored.

[0112] (1-6-6) Usage History DB 2026 Fig. 5C is a diagram showing an example of the data structure of the usage history DB 2026. A new record is recorded in the usage history DB 2026 every time the acquisition module 2032 of the server 20 acquires the usage history of the beauty device 10.

[0113] As shown in Figure 5C, the usage history DB2026 includes the items "usage history ID", "equipment ID", "treatment menu", "therapist ID", "treatment recipient information", "operating time", and "data reception date and time".

[0114] The item "usage history ID" stores usage history identification information that can identify the usage history of the beauty device 10.

[0115] The item "device ID" stores identification information of the beauty device 10 used in the usage record corresponding to the usage record ID.

[0116] The item "treatment menu" stores information about the treatment menu performed in the usage record corresponding to the usage record ID. The information about the treatment menu includes a menu ID or a menu name.

[0117] The item "practitioner ID" stores the user ID of the store staff member who performed the treatment in the usage record corresponding to the usage record ID.

[0118] The item "recipient information" stores information about the beauty salon customer who received the treatment in the usage record corresponding to the usage record ID. The customer information may be the customer's name or customer identification information managed by each beauty salon.

[0119] The item "operating time" stores information about the time during which the beauty device 10 has been operating in the usage record corresponding to the usage record ID. Specifically, the information includes the time when the beauty device 10 started operating, the time when a series of treatments ended, and the time required for the treatments.

[0120] The item "data reception date and time" stores time information about the time when the server 20 received the usage record corresponding to the usage record ID.

[0121] 5C is merely an example. The usage history DB 2026 may include columns in which other data items are stored.

[0122] (1-6-7) Device Operation Summary DB 2027 Fig. 6A is a diagram illustrating an example of the data structure of the device operation summary DB 2027. A new record is recorded in the device operation summary DB 2027 when the tallying module 2033 of the server 20 tallyes the usage record of the beauty device 10.

[0123] As shown in FIG. 6A, the device operation summary DB 2027 includes an item "operation summary ID", an item "device ID", an item "cumulative number of uses", an item "cumulative operation time", and an item "evaluation period".

[0124] The item "operation summary ID" stores identification information that can identify an operation summary, which is information that summarizes the operation status of the beauty device 10 from the summary results of the usage record of the beauty device 10.

[0125] The item "device ID" stores identification information of the beauty device 10 that is the subject of evaluation of the operation summary corresponding to the operation summary ID.

[0126] The item "cumulative number of uses" stores the cumulative number of uses of the beauty device 10 during the evaluation period included in the operation summary corresponding to the operation summary ID.

[0127] The item "cumulative operation time" stores the cumulative value of the operation time of the beauty device 10 during the evaluation period included in the operation summary corresponding to the operation summary ID.

[0128] The item "Evaluation Period" stores the period that was the subject of aggregation in the operation summary corresponding to the operation summary ID. The evaluation period can be set by the user as desired. Alternatively, a preset default value (e.g., one month) can be used as the evaluation period.

[0129] 6A is merely an example. The device operation summary DB 2027 may include columns in which other data items are stored.

[0130] (1-6-8) Treatment Summary DB 2028 Fig. 6B is a diagram showing an example of the data structure of the treatment summary DB 2028. A new record is recorded in the treatment summary DB 2028 when the tallying module 2033 of the server 20 tallyes the usage record of the beauty device 10.

[0131] As shown in Figure 6B, treatment summary DB2028 includes the items "treatment summary ID", "menu ID", "equipment type ID", "cumulative number of times performed", "cumulative treatment time", and "evaluation period".

[0132] The item "treatment summary ID" stores identification information that can identify a treatment summary, which is information that summarizes the implementation status of treatment menus from among the results of summarizing the usage history of the beauty device 10.

[0133] The item "menu ID" stores identification information of the treatment menu that is the subject of evaluation of the treatment summary corresponding to the treatment summary ID.

[0134] The item "Device Type ID" stores identification information relating to the device type of the beauty device 10 that performed the treatment menu that is the subject of evaluation of the treatment summary corresponding to the treatment summary ID.

[0135] The item "cumulative number of times performed" stores the cumulative number of times the corresponding treatment menu has been performed during the evaluation period in the treatment summary corresponding to the treatment summary ID.

[0136] The item "cumulative treatment time" stores the cumulative value of the treatment time during the evaluation period for the corresponding treatment menu in the treatment summary corresponding to the operation summary ID.

[0137] The item "Evaluation Period" stores the period that was the subject of aggregation in the treatment summary corresponding to the treatment summary ID. The evaluation period can be set by the user at will. Alternatively, a preset default value (e.g., one month) can be used as the evaluation period.

[0138] 6B is merely an example. The treatment summary DB 2028 may include columns in which other data items are stored.

[0139] 2. Overview of the Embodiment Next, an overview of the embodiment of the system 1 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an overview of the embodiment of the system 1.

[0140] (2-1) Function of tallying and displaying usage history of beauty device 10 As shown in FIG. 7 , when using the system 1, first, a store staff member at a beauty salon performs a beauty treatment on a customer using the beauty device 10. After that, the beauty device 10 wirelessly transmits the usage history to the server 20 via the network 80. The usage history is, for example, an operation log of the beauty device 10. The beauty device 10 may transmit the usage history to the server 20 each time it is used, or may transmit the usage history to the server 20 at a predetermined time interval.

[0141] Next, the server 20 tally up the usage history of the beauty device 10. At this time, the server 20 tally up the usage history of the beauty device 10 based on a preset evaluation period or a specified evaluation period.

[0142] Next, the server 20 outputs the tabulated results of the usage history of the beauty device 10 to the store terminal 30. At this time, the server 20 outputs the tabulated results of the usage history of the beauty device 10 to the store staff by displaying a dashboard on the store terminal 30. The store staff can quantitatively and intuitively grasp the usage history of the beauty device 10 by checking the tabulated results of the usage history of the beauty device 10 displayed on the dashboard.

[0143] Next, the dashboard of the system 1 will be described with reference to Fig. 8. Fig. 8 is a diagram showing the dashboard, which is an example of the first screen of the system 1. The dashboard is the screen that is first displayed when logging in to the system 1. The dashboard shows the aggregated results of usage records of the beauty device 10 for each store.

[0144] The dashboard mainly displays the following items during the evaluation period: Number of uses (C1): the number of times all beauty devices 10 owned by the store were used; Operating time (C2): the operating time of all beauty devices 10 owned by the store; Ranking (C3): the ranking of treatment menus performed using all beauty devices 10 owned by the store.

[0145] If the user is a store staff member, only the information of the store to which the user belongs is displayed. On the other hand, if the user is a store manager, the usage history of the beauty device 10 at multiple stores managed by the user is displayed. In this case, the usage history of the beauty device 10 at multiple stores may be displayed as a single graph. Furthermore, if the user is an administrator, the usage history of the beauty device 10 at all stores using the system 1 is displayed.

[0146] Here, a default value is preset for the evaluation period, which is applied when logging in. The default value is set to, for example, one month. The default value can be changed as desired. In addition, the user can execute aggregation for the specified evaluation period by entering the desired evaluation period in the period specification field C4.

[0147] The dashboard screen includes a details display field C5. The details display field C5 displays, as a summary result, the cumulative number of uses and cumulative operating hours for all beauty devices 10 used by the business operator during the evaluation period in chronological order. In the example of FIG. 8 , by clicking the first tab T1 (number of uses), the actual number of uses is displayed in a graph as time-series data for each hour. The scale of the horizontal axis of this graph can be changed as desired.

[0148] In the example of Figure 8, the bar graph shows the number of times used by hour on the current day, and the line graph shows the ratio to the number of times used in the same time frame on the previous day. In this graph, by changing the scale of the horizontal axis to days, it is possible to display time series data of the aggregated values ​​for each day during the evaluation period.

[0149] Additionally, by clicking the second tab T2 on the dashboard, the aggregated results can be displayed in chronological order of operating hours. By checking the graph, the store staff can intuitively understand the usage record of the beauty device 10. Additionally, by clicking the third tab T3, the ranking of treatment menus performed during the evaluation period can be displayed.

[0150] Next, the display of rankings of treatment menus will be described with reference to Fig. 9. Fig. 9 is a diagram showing the display of rankings of treatment menus, which is an example of the second screen of the system 1. The rankings shown in Fig. 9 are displayed on the dashboard by clicking the third tab T3 in Fig. 8.

[0151] As shown in Fig. 9, the dashboard screen displays a ranking of the cumulative number of times that treatment menus were performed during the evaluation period by all beauty devices 10 used by the business operator as a result of the aggregation. In the example shown in the figure, the ranking of treatment menus during the evaluation period is displayed on the left side, and the ranking of treatment menus during the comparison period is displayed on the right side. The evaluation period and comparison period are each written at the top of the ranking table.

[0152] The ranking also displays the cumulative number of times each treatment menu was performed during the evaluation period, visualizing the increase or decrease from the comparison period. Treatment menus whose number of times performed increased compared to the comparison period are displayed with an arrow pointing upward to the right, indicating an increase or decrease. Conversely, treatment menus whose number of times performed decreased compared to the comparison period are displayed with an arrow pointing downward to the right, indicating an increase or decrease. By checking the ranking of treatment menus, store staff can intuitively grasp the trends in the popularity of treatment menus.

[0153] In this way, the system 1 visualizes and outputs the aggregated results of the usage history of the beauty device 10, thereby providing suggestions regarding appropriate beauty treatments to stores operating beauty businesses.

[0154] (2-2) Treatment Menu Recommendation Function and Improvement Suggestion Function The system 1 also has a function of recommending a treatment menu by analyzing the aggregated results of the usage history of the beauty device 10. A recommended menu refers to a treatment menu among multiple treatment menus performed by the beauty device 10 that is recognized as contributing to the management of the store based on the usage history. Taking the initiative in implementing such a treatment menu can contribute to the management of the store.

[0155] Recommended menus include, for example, any of the following: - Treatment menus that are performed frequently - Treatment menus with high sales amounts - Treatment menus with high time productivity (sales amount / treatment time) - Treatment menus with many repeat requests

[0156] The system 1 also has a function of proposing an improvement menu by analyzing the aggregated results of the usage history of the beauty device 10. The improvement menu is a treatment menu that is deemed to be in high need of improvement in the treatment method based on the performance of the treatment. For example, an improvement menu corresponds to a treatment menu in which the operating time of the beauty device 10 varies greatly between treatments (between practitioners) even though the treatment content is the same.

[0157] Regarding such treatment menus, there is concern that the quality of beauty treatments varies due to the low level of proficiency of salon staff in the treatment menu. By identifying such improvement menus and providing training on treatments within salons, it is possible to contribute to improving the quality of beauty treatments.

[0158] (2-3) Remote Control Function by Administrator The system 1 also has a function for allowing an administrator to remotely control the beauty device 10. While salon staff have expertise in beauty, they may not be skilled in using the beauty device 10, which is an electronic device. For this reason, in the event of a malfunction in the beauty device 10, for example, the system 1 responds to an access request from the administrator terminal 40 by wirelessly communicating with the beauty device 10, allowing the administrator terminal 40 to remotely control the beauty device 10.

[0159] In the system 1, remote access software is installed in the server 20, and the beauty device 10 can be remotely controlled by logging in to the server 20 from the administrator terminal 40 and running the remote access software. This allows the administrator to properly operate the beauty device 10 even if the salon staff is unfamiliar with using the beauty device 10. The processing of the system 1 that realizes these multiple functions will be described in detail below.

[0160] 3. Operation of System 1 Next, each process performed by the system 1 will be described in detail.

[0161] (3-1) Processing for tallying usage records of the beauty device 10 First, referring to Fig. 10, a processing for tallying usage records of the beauty device 10 by the system 1 will be described. Fig. 10 is a flow chart showing processing for tallying usage records of the beauty device 10 by the system 1.

[0162] 10 , in the process of aggregating the usage history of the beauty device 10, the beauty device 10 first transmits the usage history to the server 20 (step S101). Specifically, the control unit 11 of the beauty device 10 transmits the usage history to the server 20 when the beauty device 10 is operated in response to an operation by a store staff member. The beauty device 10 transmits at least the following information to the server 20: Identification information of the beauty device 10; Details of the treatment menu indicating the treatment; Identification information of the practitioner indicating the subject of the treatment (user ID of the store staff member); and Operation start and end times of the beauty device 10.

[0163] After step S101, the server 20 receives the usage history (step S201). Specifically, the transmission / reception control module 2031 of the server 20 receives the data related to the usage history transmitted from the beauty device 10. The transmission / reception control module 2031 outputs the received data to the acquisition module 2032.

[0164] After step S201, the server 20 acquires the usage history (step S202). Specifically, the acquisition module 2032 of the server 20 acquires data related to the usage history. The acquired data includes the following information: Identification information of the beauty device 10 Contents of the treatment menu indicating the type of treatment Identification information of the practitioner indicating the subject of the treatment (user ID of the store staff member) Operating time of the beauty device 10 Date and time of data reception The acquisition module 2032 records the acquired data as a new record in the usage history DB 2026.

[0165] After step S202, the server 20 tally the usage history (step S203). Specifically, the tallying module 2033 of the server 20 tally the usage history in response to the addition of a new record to the usage history DB 2026. At this time, the tallying module 2033 refers to the usage history DB 2026 and tally the operation summaries of the beauty device 10 and the treatment summaries of the treatment menu according to a preset evaluation period. The tallying module 2033 records the tallying operation summaries as new records in the device operation summary DB 2027. The tallying module 2033 also records the tallying treatment summaries as new records in the treatment summary DB 2028. This completes the tallying process of the beauty device 10 usage history by the system 1.

[0166] (3-2) Dashboard Screen Output Processing Next, the dashboard screen output processing by the system 1 will be described with reference to Fig. 11. Fig. 11 is a flow diagram showing the dashboard screen output processing by the system 1. Note that, in this processing, an operation by the store terminal 30 will be described as an example, but the processing flow is the same when an operation is performed by the manager terminal 40.

[0167] 11 , in the dashboard screen output process, an access request is made from the store terminal 30 (step S301). Specifically, when a store staff member performs a login operation on the store terminal 30, the store terminal 30 accepts input of an account and password. The store terminal 30 transmits the account and password input as part of the login operation to the server 20.

[0168] After step S301, the server 20 accepts an access request (step S211). Specifically, the server 20 receives the user's account and password transmitted from the store terminal 30. If the received user's account and password match the account information stored in the user account DB 2021, the server 20 permits the store terminal 30 to log in to the system 1.

[0169] After step S211, the server 20 generates a dashboard screen (step S212). Specifically, the output module 2035 of the server 20 generates the dashboard screen in response to the store terminal 30 logging in to the system 1. The output module 2035 references the equipment operation summary DB 2027 and the treatment summary DB 2028 to generate a dashboard screen showing the aggregated results of usage records for each store. At this time, the output module 2035 may adjust the range of stores to be displayed based on the user authority of the logged-in user.

[0170] After step S212, the server 20 outputs the dashboard screen (step S213). Specifically, the output module 2035 of the server 20 outputs data related to the generated dashboard screen to the data transmission path established between the server 20 and the store terminal 30.

[0171] After step S213, the store terminal 30 displays the dashboard screen (step S302). Specifically, the processor 31 of the store terminal 30 accesses the data transmission path between the server 20 and the store terminal 30, performs rendering processing of the dashboard screen output from the server 20, and displays it on the output device 36. This completes the dashboard screen output processing by the system 1.

[0172] In System 1, the scope of information to be tabulated changes based on the user authority of the user making the access request. That is, the user authority of the user making the access request and the scope of devices for which usage records are to be tabulated are set as follows: Administrator authority: Devices owned by all stores of all businesses are to be tabulated Store staff authority: Devices owned by the store to which the user belongs are to be tabulated Store manager authority: Devices owned by the store (multiple stores are allowed) that the user manages are to be tabulated

[0173] (3-3) Recommended Menu Output Processing Next, the recommended menu output processing by the system 1 will be described with reference to Fig. 12. Fig. 12 is a flow diagram showing the recommended menu output processing by the system 1. Note that, in this processing, an example of operation by the store terminal 30 will be described, but the processing flow is the same when operation is performed by the manager terminal 40. Meanwhile, the range of information to be output is set based on the authority of each user.

[0174] 12 , in the recommended menu output process, a request for a recommended menu is made by the store terminal 30 (step S311). Specifically, a store staff member inputs an instruction to propose a recommended menu to the store terminal 30, and the store terminal 30 accepts the instruction. The store terminal 30 transmits the instruction to propose a recommended menu to the server 20.

[0175] After step S311, the server 20 accepts a request for proposing a recommended menu (step S221). Specifically, the server 20 receives the request for proposing a recommended menu transmitted from the store terminal 30. The request for proposing a recommended menu includes the user ID of the user who made the request for proposing.

[0176] After step S221, the server 20 identifies a recommended menu (step S222). Specifically, the identification module 2034 of the server 20 identifies the device to be analyzed based on the user's user ID. The identification module 2034 then references the results of the usage history and identifies a treatment menu that will contribute to the store's management as a recommended menu. An example of specific logic for identifying a recommended menu is provided below.

[0177] (1) When a treatment menu with a high frequency of implementation is set as the recommended menu The identification module 2034 first references the user account DB 2021 based on the user ID included in the recommendation menu proposal request to identify the store to which the user belongs as the store to be analyzed. At this time, if the user has store manager authority, multiple stores are identified as stores to be analyzed. Next, the identification module 2034 references the equipment DB 2024 to identify all equipment owned by the store to be analyzed. Then, the identification module 2034 references the treatment summary DB to identify the treatment menu that was implemented with a high frequency during the evaluation period from all equipment owned by the store. The treatment menu with a high frequency of implementation identified in this way is a popular menu and therefore corresponds to one of the recommended menus that contribute to the management of the store.

[0178] (2) When a treatment menu with a high sales amount is set as a recommended menu The identification module 2034 calculates the sales amount for each treatment menu by multiplying the treatment menu performed by all devices owned by the store being analyzed during the evaluation period, as identified as described above, by the treatment fee obtained by referencing the treatment menu DB. This allows the identification module 2034 to identify the treatment menu with the highest sales amount during the evaluation period. The treatment menu with a high sales amount during the evaluation period identified in this way corresponds to one of the recommended menus that contribute to the management of the store.

[0179] (3) When a treatment menu with high time productivity is selected as a recommended menu Time productivity in beauty treatments is evaluated by the value obtained by dividing the sales amount by the operating time (sales amount / treatment time). In other words, a treatment menu that generates high sales in a short period of time is a treatment menu with high time productivity. Therefore, when a treatment menu with high time productivity is selected as a recommended menu, the identification module 2034 calculates a time productivity index for each treatment menu by dividing the sales amount for each treatment menu calculated as described above by the cumulative treatment time stored in the treatment summary DB 2028. By comparing these indices, the identification module 2034 can identify a treatment menu with high time productivity. A treatment menu with high time productivity identified in this way corresponds to one of the recommended menus that contribute to the management of the salon.

[0180] (4) When a treatment menu with many repeat requests is set as the recommended menu A treatment menu with many repeat requests refers to a treatment menu that is repeatedly requested by the same customer. Therefore, when a treatment menu with many repeat requests is set as the recommended menu, the identification module 2034 refers to the usage history DB 2026 and tallys up the number of times the treatment menu was performed for each treated person during the evaluation period. This makes it possible to set the treatment menu with many repeat requests as the recommended menu. The treatment menu with many repeat requests identified in this way is a treatment menu that has been well received by customers and corresponds to one of the recommended menus that contributes to the management of the store.

[0181] The recommended menu that contributes to the management of the salon is not limited to the above examples. The identification module 2034 can recommend any treatment menu identified by various identification logics as long as the treatment menu is extracted from the aggregated results of the usage history of the beauty device 10.

[0182] After step S222, the server 20 outputs the identified recommended menu (step S223). Specifically, the output module 2035 of the server 20 outputs data on the identified recommended menu, together with the basis information, to the data transmission path established between the server 20 and the store terminal 30. The basis information includes the identification logic used to identify the recommended menu and data on the aggregation result of the usage history provided for the identification process.

[0183] After step S223, the store terminal 30 displays the recommended menu (step S312). Specifically, the processor 31 of the store terminal 30 accesses the data transmission path between the server 20 and the store terminal 30, and displays the recommended menu output from the server 20 together with the basis information on the output device 36. This completes the recommended menu output process by the system 1.

[0184] (3-4) Output Processing of Improvement Menu Next, the output processing of the improvement menu by the system 1 will be described with reference to Fig. 13. Fig. 13 is a flow diagram showing the output processing of the improvement menu by the system 1. Note that, in this processing, the operation by the store terminal 30 will be described as an example, but the processing flow is the same when the operation is by the manager terminal 40. Meanwhile, the range of information to be output is set based on the authority of each user.

[0185] 13 , in the improvement menu output process, a request for an improvement menu proposal is made by the store terminal 30 (step S321). Specifically, a store staff member inputs an instruction to propose an improvement menu into the store terminal 30, and the store terminal 30 accepts the instruction to propose an improvement menu. The store terminal 30 then transmits the instruction to propose an improvement menu to the server 20.

[0186] After step S321, the server 20 accepts a request for proposing an improvement menu (step S231). Specifically, the server 20 receives the request for proposing an improvement menu transmitted from the store terminal 30. The proposal request includes the user ID of the user who made the proposal request.

[0187] After step S231, the server 20 identifies an improvement menu (step S232). Specifically, the identification module 2034 of the server 20 identifies the device to be analyzed from the user ID of the user. The identification module 2034 then refers to the usage history and identifies a treatment menu that is deemed to require improvement as an improvement menu. An example of specific logic for identifying the improvement menu is provided below.

[0188] The identification module 2034 first references the user account DB 2021 based on the user ID included in the improvement menu proposal request to identify the store to which the user belongs as the store to be analyzed. At this time, if the user has store manager authority, multiple stores are identified as stores to be analyzed. Next, the identification module 2034 references the equipment DB 2024 to identify all of the equipment owned by the store to be analyzed. The identification module 2034 then references the usage history DB 2026 to identify, from among the treatment menus using the identified equipment, treatment menus whose operating times tend to vary significantly depending on the usage history. Such identified treatment menus whose operating times tend to vary significantly depending on the usage history correspond to improvement menus whose treatment methods require improvement.

[0189] The improvement menus that are deemed to be in high need of improvement in the treatment method are not limited to the above examples. The identification module 2034 can use any treatment menu identified by various identification logics as the improvement menu, as long as the treatment menu is extracted from the usage history of the beauty device 10.

[0190] After step S232, the server 20 outputs the identified improvement menu (step S233). Specifically, the output module 2035 of the server 20 outputs data on the identified improvement menu together with the basis information to the data transmission path established between the server 20 and the store terminal 30. The basis information includes the identification logic used to identify the improvement menu and data on the aggregation result of the usage record used in the identification process.

[0191] After step S233, the store terminal 30 displays the improvement menu (step S322). Specifically, the processor 31 of the store terminal 30 accesses the data transmission path between the server 20 and the store terminal 30, and displays the improvement menu output from the server 20 together with the basis information on the output device 36. This completes the improvement menu output process by the system 1.

[0192] (3-5) Remote Control Processing of the Cosmetic Device 10 Next, the remote control processing of the cosmetic device 10 by the administrator terminal 40 will be described with reference to Fig. 14. Fig. 14 is a flow chart showing the remote control processing of the cosmetic device 10 by the administrator terminal 40. Note that this processing is performed by operation from the administrator terminal 40 among the user terminals.

[0193] 14 , in the remote control process of the beauty device 10, a request for remote control is made by the manager terminal 40 (step S401). Specifically, in response to a request from a store staff member, the manager inputs a request for remote control of the beauty device 10 into the manager terminal 40. The manager terminal 40 transmits the request for remote control to the server 20.

[0194] After step S401, the server 20 accepts a request for remote control (step S241). Specifically, the transmission / reception control module 2031 of the server 20 receives the request for remote control sent from the administrator terminal 40.

[0195] After step S241, the server 20 outputs an operation screen (step S242). Specifically, the output module 2035 of the server 20 outputs the remote operation screen to the data transmission path between the server 20 and the administrator terminal 40 based on the remote operation request.

[0196] After step S242, the administrator terminal 40 displays the operation screen (step S402). Specifically, the processor of the administrator terminal 40 accesses the data transmission path between the server 20 and the administrator terminal 40, and displays the remote operation screen output from the server 20 on the output device of the administrator terminal 40.

[0197] After step S402, the administrator terminal 40 inputs a remote operation command (step S403). Specifically, the administrator inputs an operation command to the beauty device 10 according to the remote operation screen. The operation command is transmitted to the server 20.

[0198] After step S403, the server 20 executes the remote operation (step S243). Specifically, the processor 31 of the server 20 executes the remote access software to output the operation instruction for the beauty device 10 transmitted from the administrator terminal 40 to the beauty device 10.

[0199] After step S243, the beauty device 10 accepts remote control (step S111). Specifically, the control unit 11 of the beauty device 10 accepts operation instructions for the beauty device 10 input by the administrator to the administrator terminal 40 in accordance with the processing of the remote access software executed by the server 20. The control unit 11 of the beauty device 10 executes processing in accordance with the accepted operation instructions. The administrator sequentially inputs necessary operations, and the beauty device 10 executes processing based on each input operation. This completes the remote control processing of the beauty device 10 by the administrator terminal 40. An operation log related to the remote operation is linked to the identification information of the administrator, who is the operator, and stored in the memory unit 12 of the beauty device 10.

[0200] 4. Modifications Next, a modification of the system 1 will be described. In the system 1 according to the modification, the beauty device includes a high-frequency beauty device and an ultrasonic beauty device. That is, the beauty device includes a first oscillation circuit, an electromagnetic wave probe, a second oscillation circuit, and an ultrasonic probe instead of the oscillation circuit 13 and the output probe 16.

[0201] The first oscillator circuit and the electromagnetic wave probe function as a high-frequency cosmetic device. The first oscillator circuit generates a high-frequency voltage. The electromagnetic wave probe has electrodes. The high-frequency voltage generated by the first oscillator circuit is applied to the electrodes, which perform dielectric heating on the treatment area.

[0202] The second oscillator circuit and the ultrasonic probe function as an ultrasonic cosmetic device. The second oscillator circuit generates an AC signal at a predetermined frequency. The ultrasonic probe has a vibrator. The vibrator vibrates when the AC signal generated by the second oscillator circuit is applied, providing stimulation to the treatment area.

[0203] In this way, the cosmetic device according to the modified example functions as both a high frequency cosmetic device and an ultrasonic cosmetic device, and therefore a wide range of treatments can be performed with a single cosmetic device.

[0204] 5. Other Modifications Other modifications will be described below.

[0205] In the above embodiment, the recommended menu is identified by referring to the aggregated results of the usage history of the beauty device 10. However, this is not limited to this. The recommended menu may also be identified by using evaluations from customers who have received treatments. In this case, the recommended menu that contributes to the management of the salon may be identified by using the results of a questionnaire received from customers for each treatment, word-of-mouth information about the beauty salon, or the like.

[0206] Furthermore, in the system 1, the server 20 may also realize other functions. For example, the server 20 may have a lock function that restricts the use of the beauty device 10 in relation to remote operation. The lock function is used, for example, when the beauty device 10 is rented. Specifically, the lock function is used when the beauty salon is in arrears with the payment of a specified rental fee for the rental of the beauty device 10 to the equipment rental business. The administrator can turn on the lock function by operating the administrator terminal 40, thereby rendering the beauty device 10 unusable. This improves the convenience of the administrator in managing the beauty device 10.

[0207] The server 20 may also have an option management function that restricts some of the functions of the beauty device 10. The option management function is a function that enables the use of optional functions that are not included in the basic rental fee when the beauty device 10 is equipped with multiple treatment menus and a contract is made for the use of the optional functions. The administrator can enable the optional functions of the beauty device 10 at the beauty salon by operating the administrator terminal 40. This further effectively improves the convenience of the administrator in managing the beauty device 10.

[0208] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above-described embodiments. Furthermore, the above-described embodiments can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above-described embodiments and modifications can be combined, or some of them can be omitted.

[0209] 6. Supplementary Notes The matters described in the embodiment and the modified examples are supplementary notes below.

[0210] (Supplementary Note 1) A program to be executed by a server device having a processor and memory, which manages beauty equipment that provides beauty treatments to customers, the program causing the processor to perform the following steps: acquiring usage records of the beauty equipment; aggregating the acquired usage records; and, in response to an access request from a user terminal used by the user, outputting to the user terminal a dashboard screen showing the aggregated results of usage records for each store that provides the beauty treatments.

[0211] (Supplementary Note 2) In the step of acquiring usage history, the program according to Supplementary Note 1 acquires identification information of the beauty device and identification information of the practitioner who performed the beauty treatment, along with a treatment menu that indicates the content of the beauty treatment.

[0212] (Supplementary Note 3) The program according to Supplementary Note 1 or 2, wherein the dashboard screen displays, as the aggregation results, the cumulative number of uses and cumulative operating hours of all beauty devices owned by the store during the evaluation period in chronological order.

[0213] (Appendix 4) A program described in any one of Appendices 1 to 3, wherein the dashboard screen displays, as a summary result, a ranking of the cumulative number of times treatment menus indicating the contents of beauty treatments performed during the evaluation period using all beauty devices owned by the store.

[0214] (Appendix 5) The program according to Appendix 4, wherein the ranking displays the cumulative number of times each treatment menu has been performed during the evaluation period and the comparison period, with the increase or decrease from the comparison period being visualized.

[0215] (Appendix 6) A program described in any one of Appendices 1 to 5, which further causes the processor to execute the steps of: referring to usage history to identify a recommended treatment menu that will contribute to the store's management from among treatment menus that have already been performed; and outputting the identified recommended menu to a user terminal.

[0216] (Appendix 7) A program described in any one of Appendices 1 to 6, which further causes the processor to execute the steps of: referring to usage history to identify an improvement menu from among treatment menus that have already been performed that has a high variation in operating time for each cosmetic treatment; and outputting the identified improvement menu to a user terminal.

[0217] (Appendix 8) The program described in any one of Appendices 1 to 7, further causing the processor to execute a step of wirelessly communicating with the beauty device in response to an access request from an administrator terminal used by an administrator who manages the server device, and remotely operating the beauty device from the administrator terminal.

[0218] (Supplementary Note 9) A method executed by a server device having a processor and memory, and managing beauty equipment that performs beauty treatments on customers, the method comprising the steps of: acquiring usage history of the beauty equipment; aggregating the acquired usage history; and outputting to the user terminal, in response to an access request from a user terminal used by the user, a dashboard screen showing the aggregated results of usage history for each store that provides the beauty treatments.

[0219] (Supplementary Note 10) A server device comprising a processor and memory, and managing beauty equipment for providing beauty treatments to customers, wherein the processor of the server device comprises: a module for acquiring usage records of the beauty equipment; a module for aggregating the acquired usage records; and a module for outputting to the user terminal, in response to an access request from a user terminal used by the user, a dashboard screen showing the aggregated results of usage records for each store that provides the beauty treatments.

[0220] (Supplementary Note 11) A beauty management system including the server device and beauty device described in Supplementary Note 10, wherein the beauty device includes: a first oscillation circuit that generates a high-frequency voltage; an electromagnetic wave probe having an electrode to which the high-frequency voltage is applied to perform dielectric heating; a second oscillation circuit that generates an AC signal of a predetermined frequency; an ultrasonic probe having a vibrator that vibrates when the AC signal is applied; and a wireless communication module that communicates wirelessly with the server device.

[0221] The present invention can be used in the field of beauty management systems.

[0222] REFERENCE SIGNS LIST 1 Beauty management system 10 Beauty device 20 Server 21 Processor 22 Memory 23 Storage 24 Communication IF 25 Input / output IF 201 Communication unit 202 Storage unit 203 Control unit 30 Store terminal 40 Manager terminal 80 Network

Claims

1. A program to be executed by a server device having a processor and memory and managing beauty equipment that provides beauty treatments to customers, the program causing the processor to execute the following steps: acquiring usage records of the beauty equipment; aggregating the acquired usage records; and, in response to an access request from a user terminal used by a user, outputting to the user terminal a dashboard screen showing the aggregated results of the usage records for each store that provides the beauty treatments.

2. The program according to claim 1, wherein in the step of acquiring the usage history, identification information of the beauty device and identification information of the practitioner who performed the beauty treatment are acquired together with a treatment menu indicating the content of the beauty treatment.

3. The program according to claim 1, wherein the dashboard screen displays the total number of uses and total operating hours during the evaluation period for all of the beauty devices owned by the store in chronological order as the aggregation results.

4. The program described in claim 1, wherein the dashboard screen displays, as the aggregation result, a ranking of the cumulative number of times treatment menus indicating the contents of the beauty treatments performed by all of the beauty devices owned by the store during the evaluation period.

5. The program described in claim 4, wherein the ranking displays the cumulative number of times each treatment menu is performed during the evaluation period and the comparison period, with the increase or decrease from the comparison period being visualized.

6. A program described in any one of claims 1 to 5, further causing the processor to execute the steps of: referring to the usage history to identify a recommended treatment menu that will contribute to the management of the store from among treatment menus that have already been performed; and outputting the identified recommended menu to the user terminal.

7. A program described in any one of claims 1 to 5, further causing the processor to execute the steps of: referring to the usage history, identifying an improvement menu from among treatment menus that have already been performed that has a high variability in the operating time for each cosmetic treatment; and outputting the identified improvement menu to the user terminal.

8. The program according to claim 1 or 2, further causing the processor to execute a step of wirelessly communicating with the beauty device in response to an access request from an administrator terminal used by an administrator who manages the server device, and remotely controlling the beauty device from the administrator terminal.

9. A method executed by a server device having a processor and memory, which manages beauty equipment that provides beauty treatments to customers, the method comprising the steps of: acquiring usage records of the beauty equipment; aggregating the acquired usage records; and, in response to an access request from a user terminal used by a user, outputting to the user terminal a dashboard screen showing the aggregated results of the usage records for each store that provides the beauty treatments.

10. A server device comprising a processor and memory, and managing beauty equipment for providing beauty treatments to customers, wherein the processor of the server device comprises: a module for acquiring usage records of the beauty equipment; a module for aggregating the acquired usage records; and a module for outputting to the user terminal, in response to an access request from a user terminal used by the user, a dashboard screen showing the aggregated results of the usage records for each salon providing the beauty treatment.

11. A beauty management system comprising the server device of claim 10 and the beauty device, wherein the beauty device comprises: a first oscillation circuit that generates a high-frequency voltage; an electromagnetic wave probe having an electrode to which the high-frequency voltage is applied to perform dielectric heating; a second oscillation circuit that generates an AC signal of a predetermined frequency; an ultrasonic probe having a vibrator that vibrates when the AC signal is applied; and a wireless communication module that communicates wirelessly with the server device.

Images