Processing device, method, and program

Abstract

To provide a processing device, a method, and a program that can improve the efficiency of support of a target person performed by a user.SOLUTION: In a system in which a terminal device, a management server device, and a DB server device are connected to each other so that they can communicate with each other through a wireless and / or wired network, the terminal device, which is a processing device, accepts a setting operation of a task name operated by a user S101, accepts a setting operation of detailed contents of the task operated by the user S102, and accepts an allocation operation of a content ID to the task set in the steps 101 and 102, operated by the user S103.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The present disclosure relates to a processing device, a method, and a program. [Background technology]

[0002] Conventionally, there are known techniques for supporting customers in using products. For example, Patent Document 1 describes a device for promoting the use of an app by customers who use it infrequently. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-135542 Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is room for improvement in technologies for supporting target persons such as customers. The present disclosure has been made in light of the above-mentioned background, and provides a processing device, a method, and a program that enable users to efficiently support target persons. [Means for solving the problem]

[0005] According to one aspect of the present disclosure, A processing device including a processor, Based on the segment set for the target person, multiple candidate tasks for the user to perform on the target person are output; At least one of the output tasks is set as a case related to the target person. A processing device configured to is provided.

[0006] According to one aspect of the present disclosure, 1. A computer-implemented method having a processor, comprising: A step of outputting a plurality of candidate tasks to be performed by the user on the target person based on the segment set for the target person; setting at least one of the plurality of output tasks as an event related to the target person; A method including is provided.

[0007] According to one aspect of the present disclosure, A computer having a processor Based on the segment set for the target person, multiple candidate tasks for the user to perform on the target person are output; At least one of the output tasks is set as a case related to the target person. A program that makes it work like this is provided. [Effects of the Invention]

[0008] According to the present disclosure, it is possible to provide a processing device, a method, and a program that enable a user to efficiently support a subject. Note that the above effects are merely exemplary for the sake of convenience of explanation and are not limiting. In addition to or instead of the above effects, any effect described in the present disclosure or an effect that would be obvious to a person skilled in the art may be achieved. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram schematically illustrating a configuration of a system including a processing device according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the terminal device 2 according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of the management server device 3 according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram conceptually illustrating a customer information table stored in the memory 32 of the management server device 3 according to the embodiment of the present disclosure. [Figure 5]FIG. 5 is a diagram conceptually illustrating an alert information table stored in the memory 32 of the management server device 3 according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram conceptually illustrating a playbook information table stored in the memory 32 of the management server device 3 according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram showing a processing sequence executed among the terminal device 2, the management server device 3, and the DB server device 4 in the processing system 1 according to the embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram showing a processing sequence executed among the terminal device 2, the management server device 3, and the DB server device 4 in the processing system 1 according to the embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram showing a processing flow of a task setting process executed in the terminal device 2 according to an embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram showing a processing flow of a playbook setting process executed in the terminal device 2 according to an embodiment of the present disclosure. [Figure 11] FIG. 11 is an explanatory diagram showing an example of an operation screen related to the playbook setting process, which is displayed on the display of the terminal device 2. [Figure 12] FIG. 12 is a diagram showing a processing flow of the data mart generation processing executed in the terminal device 2 according to an embodiment of the present disclosure. [Figure 13] FIG. 13 is an explanatory diagram showing an example of an operation screen related to the data mart generation process, which is displayed on the display of the terminal device 2. As shown in FIG. [Figure 14] FIG. 14 is a diagram showing a processing flow of the customer setting processing executed in the terminal device 2 according to the embodiment of the present disclosure. [Figure 15] FIG. 15 is an explanatory diagram showing an example of an operation screen related to the customer setting process, which is displayed on the display of the terminal device 2. As shown in FIG. [Figure 16] FIG. 16 is a diagram showing a processing flow of the alert setting processing executed in the terminal device 2 according to an embodiment of the present disclosure. [Figure 17]FIG. 17 is an explanatory diagram showing an example of an operation screen related to the alert setting process, which is displayed on the display of the terminal device 2. As shown in FIG. [Figure 18] FIG. 18 is a diagram showing a processing flow of the alert determination processing executed in the management server device 3 according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is an explanatory diagram showing an example of an image related to the alert list 151 displayed on the display of the terminal device 2. [Figure 20] FIG. 20 is a diagram showing a processing flow of a task registration process executed in the terminal device 2 according to an embodiment of the present disclosure. [Figure 21] FIG. 21 is an explanatory diagram showing an example of an operation screen related to the task registration process, which is displayed on the display of the terminal device 2. As shown in FIG. [Figure 22] FIG. 22 is an explanatory diagram showing an example of an operation screen related to the task registration process, which is displayed on the display of the terminal device 2. [Figure 23] FIG. 23 is an explanatory diagram showing an example of an operation screen related to the task registration process, which is displayed on the display of the terminal device 2. DETAILED DESCRIPTION OF THE INVENTION

[0010] Embodiments of the present disclosure will be described with reference to the drawings, in which the same reference numerals are used to designate common components.

[0011] The processing system 1 according to the present disclosure is, for example, a system that provides a user with a task management function for a target person. In particular, the processing system is advantageously used in that it is possible to set, for example, at least one task from multiple task candidates based on a segment set for the target person as a case. In this way, in the processing system according to the present disclosure, the terminal device and the management server device can provide the user with appropriate task candidates.

[0012] In this disclosure, the terminal device 2 and the management server device 3 are described as separate devices, but they can also be used as an integrated device. Also, in this disclosure, the target simply means the target of a user's provision of information, goods, services, etc. This target may include not only individuals but also organizations such as corporations.

[0013] Furthermore, in this disclosure, a trigger condition simply means a condition for identifying a relevant event. This trigger condition may include the usage rate of a specific application (e.g., an application managed by a user), the subject's progress in work or learning, environmental factors such as weather, temperature, and humidity, and evaluations and inquiries from the subject. Furthermore, in this disclosure, a segment simply means a condition for classifying subjects. This segment may include the subject's contract status for a specific application (e.g., an application managed by a user), capital strength if the subject is a company, skills if the subject is an individual, and deliverables by the subject.

[0014] Furthermore, in this disclosure, a "case" merely refers to a matter delimited within a certain scope. This case may include goals, tasks, etc. Furthermore, in this disclosure, alert information merely refers to information provided to a user. This alert information may include announcements such as notifications, notices, warnings, and suggestions, as well as materials, etc. Furthermore, in this disclosure, a "task" merely refers to a future action. This task may include a provision action, such as the provision of goods or services, that a user makes to a target, an action that the user should take, an action that the user should have taken in the past and should take in the near future, an action that the target should take, etc. Furthermore, in this disclosure, content merely refers to information that can be perceived through the five senses. This content may include text data, audio data, the location of information on the Internet, location information, the location of physical media such as paper, etc.

[0015] Furthermore, in this disclosure, the names given to the devices are merely used to distinguish the devices from one another, and other names may be used for the devices depending on their functions.

[0016] Furthermore, in this disclosure, even if a description such as "first" or "second" is used, it does not mean that the description is limited to only the two elements to which it is attached. Naturally, multiple elements such as "third," "fourth," and more may also be included.

[0017] Fig. 1 is a diagram schematically illustrating a configuration of a system including a processing device according to an embodiment of the present disclosure. Referring to Fig. 1, the processing system 1 includes a terminal device 2, a management server device 3, and a DB server device 4. The terminal device 2, the management server device 3, and the DB server device 4 are connected to each other via a wireless and / or wired network 5 so as to be able to communicate with each other.

[0018] An example of the terminal device 2 is a portable terminal device capable of wireless communication, such as a laptop computer. The management server device 3 and the DB server device 4 store and manage various information required to execute the processing system 1, which is input to the terminal device 2, and transmit and receive various information to and from the terminal device 2. The detailed configuration and processing thereof will be described later.

[0019] In the example of FIG. 1, only one terminal device 2 is shown, but it is possible to include two or more of each device. Also, in the example of FIG. 1, two server devices, such as the management server device 3 and the DB server device 4, are shown, but there may be one, or three or more. Also, in the example of FIG. 1, the management server device 3 and the DB server device 4 are shown separately from each other, but they may be collectively referred to as server devices. However, even in such a case, this is merely a general term for each server device, and does not mean that the management server device 3 and the DB server device 4 have the same processing or configuration.

[0020] Fig. 2 is a block diagram showing an example of the configuration of a terminal device 2 according to an embodiment of the present disclosure. The terminal device 2 does not need to include all of the components shown in Fig. 2, and may have a configuration in which some components are omitted, or may include other components.

[0021] The terminal device 2 is typically a terminal device capable of wireless communication, such as a laptop computer, but is not limited to such devices. For example, the terminal device may be a feature phone, a personal digital assistant (PDA), a smartphone, a desktop computer, a portable game console, a home game console, or any other device capable of executing the program according to the present disclosure. Furthermore, the terminal device 2 in the processing system 1 may include multiple terminal devices, but the terminal devices do not need to be the same type and may be different types.

[0022] 2, the terminal device 2 includes a processor 21, a memory 22 including RAM, ROM, or non-volatile memory (or SSD in some cases), a communication interface 23 including a communication processing circuit and an antenna, an input interface 24 including a mouse, hard keys, etc., and an output interface 25. These components are electrically connected to each other via control lines and data lines.

[0023] The processor 21 is configured as a CPU (microcomputer) and functions as a control unit that controls other connected components based on various programs stored in the memory 22. Specifically, the processor 21 reads out from the memory 22 a program for executing an application according to the present disclosure and a program for executing an OS, and executes these programs. In the present disclosure, the processor 21 particularly executes the processes described in the process flows of FIGS. 9, 10, 12, 14, 16, and 20 (details of the processes are explained in FIGS. 9, 10, 12, 14, 16, 20, etc.). The processor 21 may be configured as a single CPU, or may be configured as a combination of multiple CPUs and GPUs.

[0024] The memory 22 includes a main storage device such as a ROM, RAM, or nonvolatile memory, and an auxiliary storage device such as an HDD or SSD, and functions as a storage unit. The ROM stores instructions and commands for executing the application and OS according to the present disclosure as a program. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 21. The nonvolatile memory is a memory into which data is written and read as the program is executed, and the data written therein is retained even after the execution of the program has ended.

[0025] In the present disclosure, the memory 22 particularly stores programs for executing the processes described in the process flows of Figures 9, 10, 12, 14, 16, and 20 (details of the processes will be explained in Figures 9, 10, 12, 14, 16, and 20, etc.).

[0026] The communication interface 23 functions as a communication unit that transmits and receives information to and from a remotely installed server device via a communication processing circuit and an antenna. The communication processing circuit performs processing to transmit programs and various information used in the processing system 1 to and from the server device according to the progress of processing.

[0027] The communication processing circuit processes based on a wideband wireless communication system such as the 5G system, but can also process based on a narrowband wireless communication system or a contactless wireless communication system such as a wireless LAN such as the IEEE802.11 system or Bluetooth (registered trademark). Also, wired communication can be used instead of or in addition to wireless communication.

[0028] The input interface 24 is composed of a mouse, a keyboard, etc., and functions as an input unit that accepts instruction inputs related to the execution of the program according to the present disclosure, operation inputs for registering various information, etc. The mouse accepts user operations for moving and selecting a cursor displayed on the display. The keyboard accepts user operations for typing characters. Note that, although the present disclosure uses the input interface 24 provided in the terminal device 2, it is also possible to use a touch panel that detects swipe and tap operations using, for example, a resistive film method, a capacitive coupling method, an ultrasonic surface acoustic wave method, etc.

[0029] The output interface 25 functions as an output unit that outputs images captured by the camera included in the input interface 24 and various displays output by executing the program according to the present disclosure to devices such as a display or a printer in response to instructions from the processor 21. Note that such a display may be, for example, a liquid crystal display, an organic electroluminescence display, or electronic paper.

[0030] Fig. 3 is a block diagram showing an example of the configuration of a management server device 3 according to an embodiment of the present disclosure. The management server device 3 does not need to include all of the components shown in Fig. 3, and may have a configuration in which some components are omitted, or other components may be added. Furthermore, the management server device 3 may include the components shown in Fig. 3 distributed across multiple devices.

[0031] The management server device 3 includes a processor 31 configured with a CPU or the like, a memory 32 including RAM, ROM, non-volatile memory, an HDD, and the like, and a communication interface 33. These components are electrically connected to each other via control lines and data lines. In this embodiment, a database (not shown) that stores various information may be connected via the communication interface 33. In this disclosure, the memory included in the server device may refer to only the memory 32, only the database, or both the memory 32 and the database, unless otherwise specified.

[0032] The processor 31 is configured with a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 32. In this embodiment, the processor 31 may be configured with a single CPU, or may be configured with multiple CPUs.

[0033] The memory 32 includes RAM, ROM, non-volatile memory, and HDD, and functions as a storage unit. The memory 32 stores instructions and commands for executing the application and OS according to this embodiment as a program. Such a program is loaded and executed by the processor 31. The memory 32 also stores mainly the information tables shown in FIGS. 4 to 6. The memory 32 (especially the RAM) is temporarily used to write and read data while the program is being executed by the processor 31. The memory 32 also stores mainly the information tables shown in FIGS. 4 to 6.

[0034] For example, the communication interface 33 functions as a communication unit that performs processes such as modulation and demodulation to transmit and receive programs, various information, and the like used in the system according to the present disclosure to and from the terminal device 2 via the network 5, or to and from other server devices via the network 5. The communication interface 33 communicates with other terminal devices and other server devices according to the above-mentioned wireless communication method or a known wired communication method.

[0035] FIG. 4 is a diagram conceptually illustrating a customer information table stored in the memory 32 of the management server device 3 according to an embodiment of the present disclosure. FIG. 5 is a diagram conceptually illustrating an alert information table stored in the memory 32 of the management server device 3 according to an embodiment of the present disclosure. FIG. 6 is a diagram conceptually illustrating a playbook information table stored in the memory 32 of the management server device 3 according to an embodiment of the present disclosure. Note that the information stored in each information table described below is merely an example, and it is not necessary to fulfill all of this information; information other than this information may also be stored. Furthermore, in the present disclosure, a case is described in which each information table is stored in the memory 32 of the management server device 3. However, the various tables may also be stored in the memory 22 of the terminal device 2 and the memory 32 of the DB server device 4, or may be stored in a database communicatively connected to the management server device 3 via the network 5. In this case, the management server device 3 temporarily reads the information stored in the database into the memory 32 of the management server device 3 as processing progresses and processes it.

[0036] As shown in FIG. 4, the customer information table stores "customer name," "detailed information," "segment ID," and other information associated with a customer ID. A "customer ID" is an identification number assigned to each customer. A "customer name" is the customer's company name and the name of the person in charge if the customer is a corporation, or the customer's name and nickname if the customer is an individual. A "detailed information" is detailed information about the customer. Specific examples of "detailed information" include the contract date between the user and the customer, the customer's address, telephone number, email address, and contact information such as social media accounts, company information such as capital amount and date of establishment if the customer is a company, and occupation and family composition if the customer is an individual. A "segment ID" is, for example, an identification number assigned to each segment. A segment, as will be described in more detail later, is a condition for categorizing customers. Information such as a "customer name," "detailed information," and "segment ID" associated with a customer ID may be stored individually for each customer ID, or multiple pieces of each may be stored for each customer ID.

[0037] According to FIG. 5, the alert information table stores an "alert name," a "trigger condition," a "playbook ID," and the like, in association with an alert ID. An "alert ID" is an identification number assigned to each alert. An "alert name" is information indicating the name of the alert. A "trigger condition" is information indicating the condition for notifying the user of an alert. As a specific example, a "trigger condition" may be that a customer has not used an application managed by the user for three days or more. In such a case, an example of an "alert name" is "decrease in usage rate."

[0038] The "trigger condition" stores multiple conditions. Specifically, the "trigger condition" includes a "data mart" condition, a "segment" condition, and a "user" condition. The "data mart" condition is information indicating at least one data mart in which multiple customers are registered, which is generated by the data mart generation process described below. The "segment" condition is information indicating conditions for classifying customers. The "user" condition is information indicating conditions for classifying users of the terminal device 2. For example, the "user" condition may include the user's job title, age, years of service at the company to which the user belongs, and years of work experience. In other words, the "trigger condition" is set as a condition that, when a condition for issuing an alert to a user occurs for a customer who meets the "segment" condition among the customers corresponding to the "data mart" condition, an alert is issued to a user who meets the "user" condition. Note that the "trigger condition" may include only some of the conditions listed above, or conditions other than the listed conditions may be set. In addition, information such as the "trigger conditions" ("data mart" conditions, "segment" conditions, and "user" conditions) and "playbook ID" associated with the alert ID may be stored one by one for each alert ID, or multiple of each may be stored for each alert ID.

[0039] As shown in FIG. 6, the playbook information table stores a "playbook name," a "segment ID," a "task ID," a "content ID," and the like, in association with a playbook ID. A "playbook ID" is an identification number assigned to each playbook. A "playbook name" is information indicating the name of a playbook. Here, a "playbook," as will be described in detail later, is information that compiles multiple tasks recommended to a user. A "task ID" is an identification number assigned to each task. Here, a task is information such as, for example, a provision action (such as providing goods or services) that a user performs to a customer, an action that the user should take, an action that the user should have taken in the past and should take in the near future, an action that the user should have the customer take, and the like. A "content ID" is an identification number assigned to each piece of content. Here, content is information related to the content, such as text data, audio data, the location of information on the Internet, location information, and the location of physical media such as paper, provided to the user. In addition, information such as "playbook name," "segment ID," "task ID," and "content ID" associated with a playbook ID may be stored one by one for one playbook ID, or multiple pieces of each may be stored for one playbook ID.

[0040] 7 and 8 are diagrams showing processing sequences executed among the terminal device 2, the management server device 3, and the DB server device 4 in the processing system 1 according to an embodiment of the present disclosure. The flow of processing in the processing system 1 will be described below with reference to the respective drawings.

[0041] 7, the terminal device 2 accepts an input operation of customer (target person) information by a user via the input interface 24 (S11). The terminal device 2 transmits the customer information (target person information) to the DB server device 4 via the communication interface 23, for example, in response to a user operation (T11). As a specific example, the terminal device 2 stores a portion of the customer information input in step 11 as a database in the memory 22 of the terminal device 2 at the user's discretion, and transmits the remaining portion to the DB server device 4. The DB server device 4 accumulates the received customer information in a database (DB) stored in the memory 32 (S12). In this way, by accumulating the customer information input by the user in the database stored in the memory 32 of the DB server device 4, the user can access the DB server device 4 and view the customer information. Here, one DB server device 4 has been used as an example for explanation, but multiple DB server devices may be used. This allows the user to select the most appropriate DB server device depending on the customer, etc., and accumulate the customer information in a database.

[0042] The terminal device 2 and the management server device 3 set a task by executing a task setting process (S13), which will be described in detail later. Also, the terminal device 2 and the management server device 3 set a playbook by executing a playbook setting process (S14), which will be described in detail later.

[0043] The terminal device 2 transmits a registration request to the management server device via the communication interface 23 in response to a user operation (T12). Specifically, the terminal device 2 is running an application related to the processing system 1 according to the present disclosure, and, for example, receives a user operation to register customer information stored in the memory 32 of the DB server device 4 in the application. In response to this operation, the terminal device 2 transmits a request (registration request) to the management server device 3 via the communication interface 23, instructing the management server device 3 to acquire information related to the customer information from the DB server device 4. The management server device 3, having received the registration request, transmits an acquisition request to the DB server device 4 via the communication interface 33 to request information related to the customer information (T13). The DB server device 4, having received the acquisition request, transmits information related to the customer information (acquisition response) in response to the acquisition request to the management server device 3 via the communication interface 33 (T14). Furthermore, the terminal device 2, in response to a user operation, for example, transmits a data source related to the database stored in the memory 22 to the management server device 3 via the communication interface 23 (T15). That is, the management server device 3 acquires the data source related to the acquisition response and the data source related to the database stored in the memory 22 of the terminal device 2, and stores the acquired data source in the memory 32 of the management server device 3 (S15). Note that in the above explanation, the acquisition request and acquisition response are transmitted and received between the management server device 3 and the DB server device 4, but communication may also be via the terminal device 2.

[0044] The terminal device 2 and management server device 3 execute a data mart generation process based on the data source (S16). Furthermore, the terminal device 2 and management server device 3 execute a customer setting process for each customer stored in the data mart (S17). Furthermore, the terminal device 2 and management server device 3 execute an alert setting process by the user (S18). These steps S16 to S18 will be described in detail later.

[0045] 8, the management server device 3 periodically (for example, once an hour) transmits an acquisition request to the DB server device 4 via the communication interface 33 (T21), receives an acquisition response from the DB server device 4 (T22), and receives the data source from the terminal device 2 (T23), similar to the above-described steps T13 to T15. Furthermore, similar to the above-described step S15, the management server device 3 stores the data source related to the acquisition response and the data source received from the terminal device 2 in the memory 32 (S21). Here, in step S21, the management server device 3 cumulatively stores at least a portion of the data source received in T22 and T23 in the memory 32. As a specific example, if the data source contains the date and time when the customer last used an application managed by the user, the management server device 3 cumulatively stores the date and time of the last use in the memory 32. This allows the management server device 3 to store the application usage history in chronological order in the memory 32.

[0046] As will be described in detail later, when the management server device 3 determines that an event that satisfies the alert conditions has occurred (S22), it transmits alert information to the terminal device 2 via the communication interface 33 (T24). The terminal device 2 then displays the alert information received from the management server device 3 on a display (S23). The terminal device 2 then executes task registration processing for the alert information (S24), as will be described in detail later.

[0047] FIG. 9 is a diagram illustrating a process flow of the task setting process executed in the terminal device 2 and the management server device 3 according to an embodiment of the present disclosure. The process flow of the task setting process executed in the terminal device 2 will be specifically described below. This process flow is performed, for example, by the processor 21 of the terminal device 2 reading and executing a program stored in the memory 22. The terminal device 2 accepts a user's operation to set a task name (S101). The terminal device 2 also accepts a user's operation to set detailed task information (S102). The terminal device 2 also accepts a user's operation to assign a content ID to the task set in steps S101 and S102 (S103). That is, by accepting the user's operation, the terminal device 2 acquires the task name (S101), detailed task information (S102), and a content ID assigned to the task (S103). The management server device 3 receives the information acquired by the terminal device 2 in steps S101 to S103 from the terminal device 2 via the communication interface 33 and manages the information in, for example, a task information table (not shown). Here, it is preferable that a plurality of content IDs are assigned to the task ID in step S103. More preferably, the content ID assigned to the task ID is a content group including a plurality of content IDs. That is, when the terminal device 2 receives a setting operation for a content group and assigns the content group to the task ID, it can identify a playbook related to the attribute assigned to the customer ID from among the plurality of contents linked to the content group (step S164 described later).

[0048] FIG. 10 is a diagram showing the processing flow of the playbook setting processing executed in the terminal device 2 and the management server device 3 according to an embodiment of the present disclosure. The processing flow of the playbook setting processing executed in the terminal device 2 is described in detail below. The processing flow is performed, for example, by the processor 21 of the terminal device 2 reading and executing a program stored in the memory 22. The terminal device 2 accepts a playbook name setting operation performed by a user operation (S111). The terminal device 2 also accepts a segment ID assignment operation to the playbook performed by a user operation (S112). The terminal device 2 also accepts a task assignment operation to the playbook performed by a user operation (S113). The terminal device 2 also assigns content to the task based on the content ID (S103) assigned to the task in the task setting processing (S114).

[0049] FIG. 11 is an explanatory diagram showing an example of an operation screen related to the playbook setting process displayed on the display of the terminal device 2. A playbook setting screen 101 is displayed on the display of the terminal device 2. The playbook setting screen 101 is a setting screen for accepting user operations related to the playbook setting process. This playbook setting screen 101 has a playbook selection section 103 and a detailed setting section 105. The playbook selection section 103 is, for example, a section located in the left-hand range of the playbook setting screen 101 in the horizontal direction. This playbook selection section 103 displays selection buttons 107 corresponding to the playbooks that have been set and registered, for example, lined up in a row. The selection buttons 107 are buttons that can be selected by the user.

[0050] The detailed setting section 105 is, for example, a portion enclosed by a frame arranged in the right-hand range of the playbook setting screen 101 in the horizontal direction. This playbook setting screen 101 accepts detailed settings of a playbook related to, for example, the selection button 107 selected in the playbook selection section 103. The detailed setting section 105 also includes a task setting section 109 and a segment setting section 111. The following describes, as an example, the case where the selection button 107 related to playbook G1 is selected. The task setting section 109 indicates, for example, the left-hand range of the detailed setting section 105 in the horizontal direction. This task setting section 109 has a task frame 113 arranged therein that indicates the task to be set in playbook G1. Within the task frame 113, a content display section 115 related to the content based on the content ID (S103) assigned to the task in the task setting process is arranged. The segment setting section 111 is, for example, a portion enclosed by a frame arranged in the right-hand range of the detailed setting section 105 in the horizontal direction. The segment setting unit 111 is provided with a segment display unit 117 that displays the segments set in the playbook G1.

[0051] That is, the terminal device 2 accepts a setting operation of a playbook name on the selection button 107 arranged in the playbook selection unit 103 by a user operation (S111), accepts an operation related to adding (assigning), deleting or changing the segment display unit 117 in the segment setting unit 111 (S112), and accepts an operation related to adding (assigning), deleting or changing the task frame 113 in the task setting unit 109 of the detail setting unit 105 (S113). In addition, the terminal device 2 arranges a content display unit 115 corresponding to a content ID assigned to a task related to the task frame 113 within the frame of the corresponding task frame 113 (S114). That is, by accepting a user operation, the terminal device 2 acquires setting information for the playbook name (S111), segment ID (S112) and task (S113). Furthermore, the management server device 3 receives the information acquired by the terminal device 2 in steps S111 to S113 from the terminal device 2 via the communication interface 33, and manages the information in a playbook information table as shown in FIG.

[0052] 12 is a diagram showing the processing flow of the data mart generation processing executed in the terminal device 2 according to an embodiment of the present disclosure. The processing flow of the data mart generation processing executed in the terminal device 2 will be specifically described below. This processing flow is performed, for example, by the processor 21 of the terminal device 2 reading and executing a program stored in the memory 22.

[0053] The terminal device 2 accepts a selection operation of a data source and a data mart to be registered in the data mart by a user operation (S121). The terminal device 2 also accepts a selection operation of a processing node by the user (S122). The terminal device 2 also executes a processing operation based on the data source and processing node related to the selection operation accepted in steps S121 and S122 (S123).

[0054] FIG. 13 is an explanatory diagram showing an example of an operation screen related to the data mart generation process, which is displayed on the display of the terminal device 2. The display of the terminal device 2 displays a data source aggregation unit 40, a data mart aggregation unit 50, a command aggregation unit 60, and an operation setting unit 70. The data source aggregation unit 40 is a portion surrounded by a frame with multiple source nodes 41 to 43 displayed inside. Here, a source node indicates a node linked to the corresponding data source. The source nodes 41 to 43 are nodes that can be moved or copied from the data source aggregation unit 40 to the operation setting unit 70 by a user operation. That is, when the user selects and operates the terminal device 2 to move, for example, the first source node 41 and the second source node 42 to the operation setting unit 70 (step S121), the data sources corresponding to the first source node 41 and the second source node 42 can be set in the data mart related to the generation process. The data mart aggregation unit 50 is a portion surrounded by a frame with multiple mart nodes 51 to 53 displayed inside. Here, a mart node indicates a node linked to the corresponding data mart. Similar to the source nodes 41 to 43, the mart nodes 51 to 53 are nodes that can be moved or copied from the data mart aggregation unit 50 to the operation setting unit 70 by user operation. That is, when the user selects and operates the terminal device 2 to move, for example, the first mart node 51 to the operation setting unit 70 (step S121), the data mart corresponding to the first mart node 51 can be set in the data mart related to the generation process.

[0055] The command aggregation unit 60 is a portion surrounded by a frame in which multiple command nodes 61 to 63 are displayed. Here, a command node refers to a node linked to a command executed on a data source related to a node arranged in the operation setting unit 70, such as a source node. Specific examples include a join (JOIN) node indicating a command to join multiple data sources, a select (SELECT) node that extracts at least some information from the data sources, and a grouping (GROUP BY) node that groups at least some information from the data sources. The command nodes 61 to 63, like the source nodes 41 to 43, can be moved or copied from the command aggregation unit 60 to the operation setting unit 70 by a user operation. That is, when the user selects and operates the terminal device 2 to move, for example, the first command node 61 to the operation setting unit 70, the first command node 61 can be set in the data mart related to the generation process.

[0056] The operation setting unit 70 is a framed section that displays setting information for the data mart related to the generation process and accepts new creation and changes of setting information by the user. Specifically, according to the above example, the first source node 41, the second source node 42, the first mart node 51, and the first command node 61 are arranged in the operation setting unit 70. An output node 71 indicating the operation result is also arranged in the operation setting unit 70. Lines 72 for connecting nodes are also arranged in the operation setting unit 70. The terminal device 2 accepts a user's operation to connect the nodes arranged in the operation setting unit 70 with the lines 72. For example, the terminal device 2 accepts an operation to connect the first source node 41, the second source node 42, and the first mart node 51 to the first command node 61 with the lines 72. The terminal device 2 also accepts an operation to connect the first command node 61 to the output node 71 with the lines 72. Upon receiving these operations, the terminal device 2 causes the management server device 3 to execute a calculation process to process the data source related to the first source node 41 and the data source related to the second source node 42 using a command related to the first command node 61 (S123).

[0057] In other words, the terminal device 2 can cause the management server device 3 to generate a data mart as a calculation result by accepting an operation to connect multiple nodes and the line 72. Therefore, the terminal device 2 can improve the operability for the user in generating a data mart. In particular, even if the data formats of the source nodes received by the management server device 3 are different, the terminal device 2 unifies the database format in step S15 (FIG. 7). Therefore, the user can generate a calculation result by operating based on the node indicating the name of the data source. Therefore, the terminal device 2 can improve the user operability and ultimately allow the user to focus on consideration such as the selection of the source node.

[0058] 14 is a diagram showing a processing flow of the customer setting processing executed in the terminal device 2 according to an embodiment of the present disclosure. The processing flow of the customer setting processing executed in the terminal device 2 will be specifically described below. This processing flow is mainly performed by the processor 21 of the terminal device 2 reading and executing a program stored in the memory 22. The terminal device 2 accepts an operation related to editing customer information by a user operation (S131). In addition, the terminal device 2 accepts an operation by a user operation to assign a segment to a customer (S132).

[0059] FIG. 15 is an explanatory diagram showing an example of an operation screen related to the customer setting process, which is displayed on the display of the terminal device 2. A customer information screen 121 is displayed on the display of the terminal device 2. The customer information screen 121 is a screen that displays a list of information about a customer and segments assigned to the customer. The customer information screen 121 can also accept editing operations by the user, such as adding, deleting, and changing information. The customer information screen 121 displays a customer information section 123 and a segment allocation section 125. The customer information section 123 is located, for example, in the left range in the horizontal direction of the customer information screen 121, and displays a list of information about the customer. The customer information section 123 is generated based on the customer information table ( FIG. 4 ). Specifically, the customer information table is first generated based on the data source, data mart, etc. That is, the customer information section 123 is initially generated based on the information in the data source, data mart, etc. Furthermore, when an editing operation by the user is accepted on the customer information section 123, the terminal device 2 operates the management server device 3 to edit the customer information table based on the editing operation. As a result, the customer information unit 123 can manage the customer information table with appropriate information by accepting an editing operation by the user from a state in which the table has been generated based on information from the data source, data mart, etc. (S131).

[0060] The segment assignment unit 125 is a framed section located on the right side of the customer information screen 121. The segment assignment unit 125 includes a segment display unit 127 that displays the segment to be assigned to the customer ID. When the segment assignment unit 125 receives a user operation to assign the segment display unit 127, the terminal device 2 operates the management server device 3 to edit the customer information table based on the user operation. By accepting the user's segment assignment operation, the segment assignment unit 125 can easily and appropriately assign the segment to be assigned to the customer ID. Note that the segments may be assigned based on pre-set sorting conditions, regardless of user operation, or based on the results of calculations performed by so-called AI, including a trained model capable of determining customer characteristics using a neural network or the like.

[0061] FIG. 16 is a diagram showing a processing flow of the alert setting processing executed in the terminal device 2 according to an embodiment of the present disclosure. The processing flow of the alert setting processing executed in the terminal device 2 will be specifically described below. This processing flow is mainly performed by the processor 21 of the terminal device 2 reading and executing a program stored in the memory 22. The terminal device 2 accepts a setting operation for an alert name, etc., performed by a user operation (S141). The terminal device 2 also accepts a setting operation for a trigger condition performed by a user operation (S142). The terminal device 2 also accepts an operation for assigning a playbook to an alert ID performed by a user operation (S143).

[0062] FIG. 17 is an explanatory diagram showing an example of an operation screen related to the alert setting process, which is displayed on the display of the terminal device 2. An alert setting screen 131 is displayed on the display of the terminal device 2. The alert setting screen 131 is a screen for accepting setting operations of information related to various alerts related to alert IDs by the user. This alert setting screen 131 has an alert name input unit 133, an alert description input unit 135, a trigger condition input unit 137, and a playbook assignment unit 139. The alert name input unit 133 is an input unit that accepts an input operation of an alert name for the alert ID related to the setting by the user. The alert description input unit 135 is an input unit that accepts an input operation of a description for the alert ID related to the setting by the user. In other words, the terminal device 2 accepts setting operations of the alert name, etc. by the user via the alert name input unit 133 and the alert description input unit 135 (S141).

[0063] The trigger condition input unit 137 is a framed section that can accept user input of indicators that are conditions for activating an alert for the alert ID associated with the setting. The trigger condition input unit 137 includes a condition input unit 141, a data mart input unit 143, a segment input unit 145, and a user input unit 147. The condition input unit 141 is an input unit for setting a main trigger condition. Here, the main trigger condition may be, for example, customer behavior, user behavior, or external factors (e.g., weather, stock prices, etc.) outside the customer or user. The data mart input unit 143 is an input unit for assigning a data mart containing a customer whose trigger condition is to be determined. The segment input unit 145 is an input unit for assigning a segment whose trigger condition is to be determined. The user input unit 147 is an input unit for setting a user to whom an alert is to be notified when an event that satisfies all of the conditions in the condition input unit 141, the data mart input unit 143, and the segment input unit 145 occurs. The term "user" here may refer to a specific user or may refer to a job title or the like. Specifically, when "person in charge" is set as the user input unit 147, an alert is sent only to the user who is the person in charge and who directly contacts the customer when the event occurs, and the alert is not sent to the superior of the user who is the person in charge. On the other hand, when "department manager" is set as the user input unit 147, an alert is sent only to the user who is the superior of the person in charge when the event occurs, and the alert is not sent to the user who is the person in charge.

[0064] In this way, the terminal device 2 accepts a trigger condition setting operation by the user through the condition input unit 141, data mart input unit 143, segment input unit 145, and user input unit 147 of the trigger condition input unit 137 (S142). Therefore, when the main trigger condition set in the condition input unit 141 occurs in a customer corresponding to the segment input unit 145 among the customers included in the data mart set in the data mart input unit 143, the trigger condition input unit 137 executes a notification based on alert information to the user set in the user input unit 147. Note that, although the trigger condition input unit 137 has been described above as including the condition input unit 141, data mart input unit 143, segment input unit 145, and user input unit 147, it is not necessary to perform various settings in all of these, and only some of them may be set as trigger conditions. Furthermore, the trigger condition input unit 137 is not limited to the above-mentioned input units (141 to 147), and some or all of them may be conditions different from those described above. Furthermore, as an example of information to be input into the data mart input unit 143, a data mart containing the customers to be identified has been described, but this data mart may be a data mart that has been generated in advance for use as a trigger condition, or may be the same data mart as the data mart used in the alert determination (S22).

[0065] The playbook allocation unit 139, details of which will be described later, is a boxed section that accepts an operation to assign a playbook to be used when setting a task based on a notified alert. That is, the terminal device 2 accepts an operation to assign a playbook to an alert ID by a user operation (S143). In step S143, it is possible to accept setting operations for multiple playbooks. Furthermore, in step S143, the terminal device 2 is able to accept setting operations for a playbook group linked to multiple playbooks. That is, when accepting a setting operation for a playbook group, the terminal device 2 accepts setting operations for multiple playbooks linked to the playbook group all at once. Therefore, the terminal device 2 can identify a playbook related to an attribute assigned to a customer ID from among the multiple playbooks linked to the playbook group. Furthermore, by accepting a setting operation for a playbook group by the user, the terminal device 2 can simplify the user's playbook setting operation for setting multiple playbooks.

[0066] 18 is a diagram showing the processing flow of the alert determination processing executed in the management server device 3 according to an embodiment of the present disclosure. The processing flow of the alert determination processing executed in the management server device 3 will be specifically described below. This processing flow is mainly performed by the processor 31 of the management server device 3 reading and executing a program stored in the memory 32. The management server device 3 determines whether an event corresponding to the trigger condition has occurred (S151), and repeatedly executes step S151 until it determines that an event corresponding to the trigger condition has occurred (No), and when it determines that an event corresponding to the trigger condition has occurred (Yes), it proceeds to step S152.

[0067] As a specific example, assume that the trigger condition input unit 137 has "no access to a specified web page for three days" set in the condition input unit 141, "data mart Ea1" set in the data mart input unit 143, and "high-value subscriber" set in the segment input unit 145. In this case, in step S151, when the management server device 3 detects that "no access to a specified web page for three days" (Yes) for a customer included in "data mart Ea1" who is assigned the segment "high-value subscriber," the management server device 3 proceeds to step S152.

[0068] The management server device 3 identifies customers that meet the trigger conditions (S152). Specifically, among the customers included in the data mart set in the data mart input unit 143 and that meet the segment set in the segment input unit 145, the management server device 3 identifies customers that meet the trigger conditions set in the condition input unit 141. Note that there may be multiple customers identified in step S152.

[0069] The management server device 3 identifies a segment ID corresponding to the customer ID of the customer identified in step S152 based on the customer information table (FIG. 4) (S153). Then, the management server device 3 generates alert information including information such as the customer information of the customer identified in step S152, the segment ID assigned to the customer identified in step S153, and the alert name (S154).

[0070] Here, the segment IDs set by the segment input unit 145 in the setting of the trigger condition (S142) described above are stored in the alert information table (FIG. 5). For example, in the customer information table (FIG. 4), the segment IDs assigned to "customer ID" A1 are "segment IDs" B1, B2, and B3, the segment IDs assigned to "customer ID" A2 are "segment IDs" B1, B4, and B5, and the segment IDs assigned to "customer ID" A3 are "segment IDs" B2, B3, and B4. Also, in this example, the segment ID assigned to "alert ID" C1 is "segment ID" B1. In such a case, since the inclusion of "segment ID" B1 is part of the trigger condition, the customers identified in step S152 when the answer is Yes in step S151 are "customer ID" A1 and "customer ID" A2, which include "segment ID" B1. Meanwhile, in step S153, "segment IDs" B1, B2, and B3 are identified for "customer ID" A1, and "segment IDs" B1, B4, and B5 are identified for A2. Therefore, by identifying a segment ID for each customer identified in steps S151 and S152 based on the customer information table (FIG. 4), the management server device 3 can identify a different segment for each identified customer and generate alert information (S154).

[0071] FIG. 19 is an explanatory diagram showing an example of an image related to the alert list 151 displayed on the display of the terminal device 2. The alert list 151 is a list in which multiple pieces of alert information 153 (items) received (T24) from the management server device 3 via the communication interface 23 are arranged vertically (columnwise). Here, the alert information 153 is displayed to include, for example, the following items: alert name, customer name, trigger, status, deadline, and person in charge. The alert name is the name of the alert identified based on the "alert ID." The customer name is the name of the customer identified based on the customer ID stored in the customer information table. The trigger is the name of the trigger condition stored in the customer information table. The status is information indicating the progress of the user's response to the task assigned to the alert information 153. The deadline is information indicating the deadline for completing the task assigned to the alert information 153. The person in charge is displayed, for example, as the name of the user operating the terminal device 2. The title of the alert information 153 may be a string of numbers like the management number of the alert information 153, as long as it is possible to identify the alert information 153. The trigger may be a description of the trigger condition or an abbreviation, as long as it can identify the trigger. The status may display the ratio of the number of completed tasks to the total number of tasks for each alert information 153, or may be manually entered by the user. The deadline may be the oldest deadline among the tasks assigned to the alert information 153, or may be the deadline for completing the tasks assigned to the alert information 153.

[0072] Here, the order of the alert information 153 in the vertical direction is determined according to the segment. Specifically, the terminal device 2 identifies the customer segment based on the customer ID associated with the customer name. Then, according to the priority associated with the segment, the cases are displayed in order of priority, with the highest priority being at the top. This allows the user to manage the cases in the alert list 151 in the vertical direction, starting from the top, and perform tasks in order of priority.

[0073] 20 is a diagram showing a processing flow of the task registration processing executed in the terminal device 2 according to an embodiment of the present disclosure. The processing flow of the task registration processing executed in the terminal device 2 will be specifically described below. This processing flow is mainly performed by the processor 21 of the terminal device 2 reading and executing a program stored in the memory 22. The terminal device 2, details of which will be described later, displays a playbook selection screen 161 (S161) and accepts a playbook selection operation by the user (S162).

[0074] FIG. 21 is an explanatory diagram showing an example of an operation screen related to task registration processing, which is displayed on the display of the terminal device 2. For example, when a user selects (e.g., clicks on) alert information 153, an alert details screen 155 is overlaid on the alert list 151. The alert details screen 155 is a screen on which the details of the alert information 153 selected by the user can be confirmed. This alert details screen 155 has multiple tabs 156. When a user selects one of the multiple tabs 156, information related to the selected tab is displayed below the tab 156 (hereinafter referred to as a detail display section 157) on the display of the terminal device 2. In the example of FIG. 21, the "Task" tab 156 is selected. If a task has not been set in the alert information 153, for example, "Not Set" is displayed in the detail display section 157 for "Task." Furthermore, a manual button 158 and a playbook selection button 159 are displayed below the detail display section 157 for "Task." When the manual button 158 is selected, a setting screen (not shown) is displayed on the display, allowing the user to add task settings such as the task name at their discretion. When the playbook selection button 159 is selected, a playbook selection screen 161 (FIG. 21) is displayed on the display.

[0075] FIG. 22 is an explanatory diagram showing an example of an operation screen related to the task registration process, which is displayed on the display of the terminal device 2. When the playbook selection button 159 is selected as described above, a playbook selection screen 161 is displayed on the display of the terminal device 2 (S161). The playbook selection screen 161 displays multiple playbook candidates 163 arranged vertically. Each playbook candidate 163 displays a match rate. The match rate is a value calculated based on the degree of match between the segment ID corresponding to the customer ID of the customer identified in step S153 and the segment ID identified for each playbook candidate 163 based on the playbook information table (FIG. 6). The multiple playbook candidates 163 are arranged so that the higher the match rate, the higher they are positioned at the top of the playbook selection screen 161. Therefore, by setting a segment ID for each customer ID and playbook ID, the terminal device 2 can preferentially recommend appropriate playbooks to the user based on the segment, starting from the top.

[0076] The terminal device 2 accepts a user's selection operation for one of the multiple playbook candidates 163 lined up on the playbook selection screen 161 (S162). Here, when the user views the multiple playbook candidates 163, it is conceivable that the user will select one of the playbook candidates 163 based on factors other than the segment (for example, the user's expectations of the customer). In other words, the terminal device 2 allows the user to select a more appropriate playbook by leaving the selection of one of the multiple playbook candidates 163 to the user's operation.

[0077] Returning to FIG. 20, the terminal device 2 assigns a task to the alert information 153 based on the playbook ID of the selected playbook (S163). Furthermore, based on the playbook information table (FIG. 6), the terminal device 2 identifies a content ID corresponding to the task ID assigned to the alert information 153 in step S163, the content ID assigned to the selected playbook, and the content ID assigned to the customer, and assigns the content ID to the alert information 153 (S164). Specifically, of the multiple content IDs assigned to the task ID in the above-mentioned step S103, content corresponding to the attribute assigned to the customer ID is assigned to the alert information 153. In particular, when a content group including multiple content IDs is assigned to the task ID, the terminal device 2 can identify content related to the attribute assigned to the customer ID from the multiple contents linked to the content group.

[0078] FIG. 23 is an explanatory diagram showing an example of an operation screen related to the task registration process, displayed on the display of the terminal device 2. As a result, when the "Task" tab 156 is selected, the task 171 corresponding to the playbook ID of the selected playbook is displayed in the details display section 157. Therefore, the terminal device 2 can set a task to alert information based on the selected playbook, thereby reducing the effort required for the user to set a task. In particular, because a task is identified by selecting a playbook, the terminal device 2 can standardize task setting by users, thereby suppressing personal task management by users.

[0079] Furthermore, a corresponding content button 173 is arranged in the task 171. That is, the terminal device 2 displays the content button 173 in the task 171 in the details display section 157. The content button 173 is a button that can receive a selection operation by the user. When the user selects one of the multiple content buttons 173 displayed in the details display section 157, the terminal device 2 displays the content corresponding to the selected content button 173 on the display. This allows the terminal device 2 to reduce the user's work of searching for content related to the task. In particular, since content is identified along with the task by selecting a playbook, the terminal device 2 can standardize the content provided by the user to customers, and ultimately suppress the provision of personal content by users.

[0080] With the above-described configuration, the terminal device 2 according to the present disclosure outputs, to the display, a plurality of candidate tasks for the user to perform on the customer based on the segment set for the customer as the target (S161), and sets at least one of the plurality of output tasks as a case related to the target (S24). Similarly, the management server device 3 according to the present disclosure outputs, to the terminal device 2, a plurality of candidate tasks for the user to perform on the customer based on the segment set for the customer as the target (S18, S22, T24), and sets at least one of the plurality of output tasks as a case related to the target (S24). As a result, the terminal device 2 and management server device 3 according to the present disclosure can provide the user with a case including a task appropriate for the customer by setting at least one task as a case from the candidate tasks based on the segment set for the customer.

[0081] Furthermore, in the present disclosure, the terminal device 2 and the management server device 3 use a playbook, which is a collection of task candidates, and accept a user's operation to select at least one playbook from multiple playbooks, thereby reducing the user's effort in setting tasks. Furthermore, since the playbook selection screen 161 includes playbook candidates 163 (task information), which are tasks recommended to the user, the terminal device 2 and the management server device 3 can allow the user to consider tasks for the event that has occurred with reference to the playbook selection screen 161. In particular, since some users may have low proficiency in supporting customers, the terminal device 2 and the management server device 3 can recommend appropriate tasks to users with low proficiency, thereby supporting the users.

[0082] Furthermore, when an event corresponding to a trigger condition occurs, the terminal device 2 and management server device 3 according to the present disclosure output, for example, to a display, alert information (FIG. 19) corresponding to a segment set for a customer identified based on the trigger condition (S23).When an event corresponding to the trigger condition (FIG. 5) occurs (S151), alert information corresponding to a segment (S153) set for a customer identified based on the trigger condition is output (T24).

[0083] As a result, the terminal device 2 and management server device 3 according to the present disclosure can provide the user with alert information based on the customer segment identified based on the trigger condition. The terminal device 2 and management server device 3 according to the present disclosure can assign the user's tasks related to the trigger condition based on the playbook by having the user select one playbook from the playbook candidates 163 on the playbook selection screen 161. Therefore, the terminal device 2 and management server device 3 according to the present disclosure can improve the efficiency of the user's support for customers.

[0084] In addition, in the present disclosure, the playbook selection screen 161 is specified based on the segment (S163), so that tasks appropriate for the customer can be specified based on the segment. In particular, by setting tasks in association with the segment in step S163, tasks can be set more easily for each customer than when tasks are set manually, for example.

[0085] Furthermore, in the present disclosure, the playbook selection screen 161 includes a content button 173 indicating content to be presented to the customer, thereby saving the user the trouble of searching for content information. In particular, the terminal device 2 and the management server device 3 can recommend appropriate content to be presented to the customer to a user with a low level of proficiency. In addition, in the present disclosure, content information is identified based on a segment, so that content information appropriate for the customer can be identified based on the segment. In particular, by setting content in association with a segment in step S164, content can be set more easily than when content is set for each customer.

[0086] Furthermore, in the present disclosure, a data source containing information about multiple customers is obtained from the DB server device 4 as an external device (T14), and segment settings for each of the multiple customers included in the data source are accepted (S132), so that the terminal device 2 and the management server device 3 can set segments for each customer using information about customers that the user has previously stored in the DB server device 4.

[0087] Furthermore, in the present disclosure, the user is allowed to select source nodes 41 and 42 from source nodes 41 to 43, which represent multiple types of data sources, and to link a first command node 61, which represents a join command, to source nodes 41 and 42, thereby allowing the user to experience intuitive and simple data mart generation.

[0088] Furthermore, in the present disclosure, the display mode of the alert list as alert information is determined according to the priority associated with the segment. Therefore, for example, by displaying cases vertically from highest priority to lowest, the user can be encouraged to manage cases vertically from the top of the alert list and complete the cases in the optimal order.

[0089] In the above-described embodiment, the processes according to the present disclosure have been described, but the processes may be implemented in an embodiment in which each process is appropriately combined. Furthermore, the execution entities of the processes according to the present disclosure are not limited to those described above; some or all of the processes may be executed by different entities. For example, in the above-described embodiment, the task setting process (S13), playbook setting process (S14), datamart generation process (S16), customer setting process (S17), alert setting process (S18), and task registration process (S24) are executed by the terminal device 2 and the management server device 3. However, they may be executed by either the terminal device 2 or the management server device 3. Furthermore, in the above-described embodiment, it has been described that the data source storage (S15, S21) and the alert determination (S22) are executed in the management server device 3. However, by storing the data source in the memory 22 of the terminal device 2 and executing the task setting process (S13), the playbook setting process (S14), the data mart generation process (S16), the customer setting process (S17), the alert setting process (S18), and the task registration process (S24) in the terminal device 2, the processing from step S13 onwards may be executed in the terminal device 2 without relying on the management server device 3. Similarly, by executing the task setting process (S13), the playbook setting process (S14), the data mart generation process (S16), the customer setting process (S17), the alert setting process (S18), and the task registration process (S24) in the management server device 3, the processing of steps S13 to S22 may be executed in the management server device 3 without relying on the terminal device 2.

[0090] Furthermore, the processes and procedures described herein may be implemented not only by those explicitly described in this disclosure, but also by software, hardware, or a combination thereof. Specifically, the processes and procedures described herein may be implemented by implementing logic corresponding to the processes in media such as integrated circuits, volatile memory, nonvolatile memory, magnetic disks, and optical storage. Furthermore, the processes and procedures described herein may be implemented as computer programs and executed by various computers, including terminal devices and server devices.

[0091] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, multiple software, multiple components, and / or multiple modules. Furthermore, although various information described herein is described as being stored in a single memory or storage unit, such information may be stored in multiple memories within a single device or multiple memories distributed across multiple devices. Furthermore, software and hardware elements described herein may be realized by integrating them into fewer components or by decomposing them into more components. [Explanation of symbols]

[0092] 2. Terminal equipment (processing equipment) 3. Management server device (processing device) 4. DB server device

Claims

1. A processing device including a processor, Based on the segment set for the target person, multiple candidate tasks for the user to perform on the target person are output; At least one of the output tasks is set as a case related to the target person. A processing device configured to:

2. The output includes a plurality of playbooks, each of which is a set of candidate tasks; The setting is performed by accepting a selection operation by the user of at least one playbook from the plurality of playbooks output by the output. The processing device of claim 1 .

3. When an event occurs that corresponds to the trigger condition, outputting a plurality of candidate tasks corresponding to the segments set for the target person identified based on the trigger condition; The processing device according to claim 1 , configured to:

4. The case includes content information indicating content to be presented to the target person. The processing device of claim 1 .

5. the content information is identified based on the segment; The processing device according to claim 4 .

6. Obtaining a data source containing a plurality of pieces of information about the subject from an external device; Accepting the setting of the segment for each of the plurality of subjects included in the data source; The processing device according to claim 1 , configured to:

7. accepting an operation by a user to select two or more source nodes from source nodes indicating each of the plurality of types of data sources, and an operation to link a node indicating a join command to the two or more source nodes; The processing device of claim 6 .

8. The processing device according to claim 1 , configured to determine a display manner of the candidate tasks depending on a priority associated with the segment.

9. 1. A computer-implemented method having a processor, comprising: A step of outputting a plurality of candidate tasks to be performed by the user on the target person based on the segment set for the target person; setting at least one of the plurality of output tasks as an event related to the target person; A method comprising:

10. A computer having a processor Based on the segment set for the target person, multiple candidate tasks for the user to perform on the target person are output; At least one of the output tasks is set as a case related to the target person. A program that makes it work like this.

Images